A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-February/086141.html below:

[Python-Dev] No 2.x->3.x porting documentation?

[Python-Dev] No 2.x->3.x porting documentation? [Python-Dev] No 2.x->3.x porting documentation?Benjamin Peterson benjamin at python.org
Mon Feb 16 04:05:57 CET 2009
On Sun, Feb 15, 2009 at 8:59 PM,  <skip at pobox.com> wrote:
> If neither of these changes could be handled by 2to3 I think it would have
> been useful to at least document the changes (in whatsnew/3.0.rst?) and
> maybe offer humans some workaround ideas.  If there is a wiki page
> collecting porting wisdom it should be referenced.  If I'm missing something
> fundamental about how people are expected to approach porting 2.x code to
> 3.x, please let me know.

All your points are valid. See http://wiki.python.org/moin/PortingToPy3k

Please contribute if you can!



-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

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