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 note in the porting HOWTO mentioning that you should always special-case Python 2 code and not Python 3 code.
---------- assignee: docs@python components: Documentation messages: 258126 nosy: brett.cannon, docs@python priority: normal severity: normal status: open title: Update porting HOWTO to special-case Python 2 code, not Python 3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26095> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
