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 larry
Recipients larry
Date 2011-10-01.10:57:41
SpamBayes Score 2.4701558e-08
Marked as misclassified No
Message-id <1317466662.3.0.331555988129.issue13086@psf.upfronthosting.co.za>
In-reply-to
Content
The title of howto/cporting.rst is "Porting Extension Modules To 3.0".  It then talks about 3.0 in a whole bunch of places.  Considering that we're working on 3.3, and considering that 3.0 is end-of-lifed (not even meriting a branch in hg), wouldn't it be better for the document to talk about "3.x"?  It already talks about "2.x" in several places, so it's not like this would confuse the reader.

Alternatively, we could remove the ".0" (and maybe the ".x"s) so the document talks about porting from "Python 2" to "Python 3".

I'd be happy to make the patch / check in the change.
History
Date User Action Args
2011-10-01 10:57:42larrysetrecipients: + larry
2011-10-01 10:57:42larrysetmessageid: <1317466662.3.0.331555988129.issue13086@psf.upfronthosting.co.za>
2011-10-01 10:57:41larrylinkissue13086 messages
2011-10-01 10:57:41larrycreate