[issue8127] Add link to PortingPythonToPy3k to What's New documentation

R. David Murray added the comment: Raymond, I'm adding you as nosy even though I'm closing the issue as out of date in case you do want to add a link in the 3.2 What's New. -- nosy: +r.david.murray, rhettinger resolution: -> out of date status: open -> closed type: -> feature request

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Andrew McNabb added the comment: Thanks for your advice. I just signed up for the python-porting list, and I'll start a discussion there. I'm trying to improve the wiki page to address your concerns. There are multiple valid approaches to take, and I'm trying to make the page show this. I

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Martin v. Löwis added the comment: Andrew McNabb wrote: > Andrew McNabb added the comment: > > By the way, I just noticed your notes on the wiki page and added a > response/question. It seems that the advice that you consider bad is > the official porting story (upgrade to 2.6 and use 2to3).

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Martin v. Löwis added the comment: > What advice in particular do you consider bad? I would be happy to > submit some changes to the wiki page for anything that's wrong. See my comments on the page. The first headline is IMO fairly counter-productive, as it (essentially) suggests that you can'

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Andrew McNabb added the comment: By the way, I just noticed your notes on the wiki page and added a response/question. It seems that the advice that you consider bad is the official porting story (upgrade to 2.6 and use 2to3). I agree that it's easier and better to not drop support for 2.4

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Andrew McNabb added the comment: What advice in particular do you consider bad? I would be happy to submit some changes to the wiki page for anything that's wrong. I think it would be great to have a reviewed version in the documentation directly, but I think the world needs a little more ex

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

Martin v. Löwis added the comment: -1. The page contains bad advice, and shouldn't be recommended in its current form. That probably could be fixed, but points to the core problem: in the wiki, anybody can add text, even if it's not properly reviewed. It would IMO be better if a reviewed an

[issue8127] Add link to PortingPythonToPy3k to What's New documentation

New submission from Andrew McNabb : The What's New documentation for Python 3.0 and 3.1 have sections called "Porting to Python 3.0". It would be great to add a link to the Python wiki page about porting Python to Python 3: http://wiki.python.org/moin/PortingPythonToPy3k -- assignee: