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 terry.reedy
Recipients georg.brandl, gvanrossum, nedbat, pitrou, techtonik, terry.reedy
Date 2013-02-03.20:56:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359924992.96.0.769514366269.issue7083@psf.upfronthosting.co.za>
In-reply-to
Content
Anatoly, please stop playing with the headers. It is meaningless and irritating, especially when you set them wrong. The 3.5 choice is for issues that will *not* apply before then. An example is actually making a change warned about in a deprecation warning. 3.2 will soon see its last regular bugfix release. The main purpose of the headers is to help developers develop and apply a patch. The secondary purpose is serve as history and to inform users.

As I explained in my email to you
1. The OP meant for this to be a code bug report.
2. This was properly closed as an invalid bug report. So there will be no code patch. So the headers have no use except as history.
3. I do believe the doc should be changed, *and* I believe it should be a new issue. If I do open one, I will try to remember to add it here as superseder.
History
Date User Action Args
2013-02-03 20:56:33terry.reedysetrecipients: + terry.reedy, gvanrossum, georg.brandl, pitrou, techtonik, nedbat
2013-02-03 20:56:32terry.reedysetmessageid: <1359924992.96.0.769514366269.issue7083@psf.upfronthosting.co.za>
2013-02-03 20:56:32terry.reedylinkissue7083 messages
2013-02-03 20:56:32terry.reedycreate