On Fri, Dec 5, 2014, at 18:16, Donald Stufft wrote: > > > > On Dec 5, 2014, at 6:10 PM, Brett Cannon <bcannon at gmail.com> wrote: > > > > > > > > On Fri Dec 05 2014 at 4:07:46 PM Benjamin Peterson <benjamin at python.org <mailto:benjamin at python.org>> wrote: > > > > > > On Fri, Dec 5, 2014, at 16:04, Brett Cannon wrote: > > > It now promotes using tooling as much as possible to automate the process > > > of making code by Python 2/3 source-compatible: > > > https://docs.python.org/3.5/howto/pyporting.html <https://docs.python.org/3.5/howto/pyporting.html> > > > > Are you going to update the 2.7 copy of the howto, too? > > > > Have not decided yet. All the Google searches I have tried that bring up the HOWTO use the Python 3 version. Plus I know people are going to find mistakes that require fixing so I would rather wait until it stabilizes before I bother backporting to 2.7. > > _______________________________________________ > > Python-Dev mailing list > > Python-Dev at python.org > > https://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io > > > Do we need to update it? Can it just redirect to the 3 version? Technically, yes, of course. However, that would unexpected take you out of the Python 2 docs "context". Also, that doesn't solve the problem for the downloadable versions of the docs.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4