[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-03-20 Thread Roundup Robot
Roundup Robot added the comment: New changeset a2bf6d1e018e by Brett Cannon in branch 'default': Merge for issue #26095 https://hg.python.org/cpython/rev/a2bf6d1e018e -- nosy: +python-dev ___ Python tracker ___

[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-03-19 Thread Brett Cannon
Changes by Brett Cannon : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-01-22 Thread Brett Cannon
Changes by Brett Cannon : -- assignee: docs@python -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-01-12 Thread Nick Coghlan
Nick Coghlan added the comment: The feature detection approach is especially important for anything covered by the security backports in PEP 466 and 476, but can also apply for things like installing the importlib2 meta_path hooks into Python 2.7. -- nosy: +ncoghlan __

[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-01-12 Thread Brett Cannon
Brett Cannon added the comment: And suggesting feature detection is even better than version detection. -- ___ Python tracker ___ ___

[issue26095] Update porting HOWTO to special-case Python 2 code, not Python 3

2016-01-12 Thread Brett Cannon
New submission from Brett Cannon: 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