This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients amcnabb, ezio.melotti, georg.brandl, loewis
Date 2010-03-12.21:34:59
SpamBayes Score 6.879436e-09
Marked as misclassified No
Message-id <4B9AB381.9050006@v.loewis.de>
In-reply-to <1268427793.84.0.395193732219.issue8127@psf.upfronthosting.co.za>
Content
> 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't start
supporting 3.x until you can leave 2.5 behind - which for most projects
will still be several years in the future.

> Right now, there's no sense of best practices in porting to Python 3,
> and it's leaving people with the impression that it's too hard and
> not worth it.

Then discuss the page and its contents on the python-porting list.
History
Date User Action Args
2010-03-12 21:35:00loewissetrecipients: + loewis, georg.brandl, amcnabb, ezio.melotti
2010-03-12 21:34:59loewislinkissue8127 messages
2010-03-12 21:34:59loewiscreate