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.20:28:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't want to be distracted by "new in 3.1" tags when reading
> the 3.6 documentation.

This is true, but on the other hand you might want to see the [new in 3.4] while looking at 3.6 docs and working on a program that must support Python 3.3+.  Anyway we can discuss this again once we have a patch -- depending on how it is implemented, it might be easy enough to include the tag only for functions added in the last 2 releases, or perhaps the tag won't be particularly distracting and can be used for all versions.
Date User Action Args
2015-10-26 20:28:49ezio.melottisetrecipients: + ezio.melotti, brett.cannon, georg.brandl, eric.araujo, r.david.murray, docs@python, Tony R.
2015-10-26 20:28:49ezio.melottisetmessageid: <>
2015-10-26 20:28:49ezio.melottilinkissue25467 messages
2015-10-26 20:28:49ezio.melotticreate