➜

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 brett.cannon
Recipients brett.cannon, docs@python
Date 2016-01-13.02:16:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452651397.71.0.110404454924.issue26095@psf.upfronthosting.co.za>
In-reply-to
Content 
As pointed out by http://astrofrog.github.io/blog/2016/01/12/stop-writing-python-4-incompatible-code/, special-casing Python 3 code instead of Python 2 code when writing Python 2/3 code will lead to breakage when Python 3 comes out. There should probably be a note in the porting HOWTO mentioning that you should always special-case Python 2 code and not Python 3 code.
History
Date User Action Args
2016-01-13 02:16:37brett.cannonsetrecipients: + brett.cannon, docs@python
2016-01-13 02:16:37brett.cannonsetmessageid: <1452651397.71.0.110404454924.issue26095@psf.upfronthosting.co.za>
2016-01-13 02:16:37brett.cannonlinkissue26095 messages
2016-01-13 02:16:36brett.cannoncreate