This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients Tony R., brett.cannon, docs@python, eric.araujo, ezio.melotti, georg.brandl, r.david.murray
Date 2015-10-26.17:49:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445881786.52.0.901717620528.issue25467@psf.upfronthosting.co.za>
In-reply-to
Content
> Note that the 'new' label should only appear for stuff that is new
> in that release.

This is not a problem if it says [new in x.y] explicitly.  This way for each version-added/version-changed/deprecated/deprecated-remove directive we will also have a label.

As for the implementation, I'm pretty sure it can be done by changing/redefining all the function/method/class directives.  The directives should then be able to inspect the nodes they contain and see if there are any of the aforementioned directives and turn them into labels.  Not sure if there's a clever way to do it though (maybe a CSS class can be added to the directives and the labels can be added with CSS :after).
History
Date User Action Args
2015-10-26 17:49:46ezio.melottisetrecipients: + ezio.melotti, brett.cannon, georg.brandl, eric.araujo, r.david.murray, docs@python, Tony R.
2015-10-26 17:49:46ezio.melottisetmessageid: <1445881786.52.0.901717620528.issue25467@psf.upfronthosting.co.za>
2015-10-26 17:49:46ezio.melottilinkissue25467 messages
2015-10-26 17:49:46ezio.melotticreate