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 josh.r
Recipients brett.cannon, josh.r
Date 2014-04-16.11:17:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397647024.56.0.205268352345.issue21237@psf.upfronthosting.co.za>
In-reply-to
Content
I think the suggestion is intended for "how do I keep Python 2 semantics in Python 3?", not "how can I write my Python 2 code so it will run equivalently in Python 3?"

It wouldn't be a bad idea to point out that you can adopt Py3 semantics initially so as to avoid surprises later on; sadly, unlike a __future__ import, if you want cross compatible code you have to do stupid stuff like:

try:
    from future_builtins import *
except ImportError:
    # Py3 is already the future
    pass
History
Date User Action Args
2014-04-16 11:17:04josh.rsetrecipients: + josh.r, brett.cannon
2014-04-16 11:17:04josh.rsetmessageid: <1397647024.56.0.205268352345.issue21237@psf.upfronthosting.co.za>
2014-04-16 11:17:04josh.rlinkissue21237 messages
2014-04-16 11:17:04josh.rcreate