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 nikratio
Recipients Claudiu.Popa, docs@python, eli.bendersky, eric.araujo, ezio.melotti, georg.brandl, nikratio, scoder
Date 2014-03-31.16:37:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396283877.11.0.356114317916.issue20375@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, the new testcases were deliberately included. I submitted the patch prior to the 3.4 release, am I right that at that point this wouldn't have been a problem?

I have attached a new patch containing just the doc changes. I hope that's still acceptable for inclusion in 3.4 (and maybe 3.3? not sure if there'll be another bugfix release).
History
Date User Action Args
2014-03-31 16:37:57nikratiosetrecipients: + nikratio, georg.brandl, scoder, ezio.melotti, eric.araujo, eli.bendersky, docs@python, Claudiu.Popa
2014-03-31 16:37:57nikratiosetmessageid: <1396283877.11.0.356114317916.issue20375@psf.upfronthosting.co.za>
2014-03-31 16:37:57nikratiolinkissue20375 messages
2014-03-31 16:37:57nikratiocreate