[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-07 Thread Terry J. Reedy
Terry J. Reedy added the comment: Yes, 'to Python 3'. Patch welcome. I would make it up to date as of 3.2. For 3.3, the Unicode api will change (grow) but that has not been finalized yet. -- nosy: +terry.reedy versions: +Python 2.7 ___ Python tracke

[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-01 Thread Martin v . Löwis
Martin v. Löwis added the comment: I like "Python 2" more than "2.x". -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list ma

[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-01 Thread Georg Brandl
Georg Brandl added the comment: 3.1 because it won't have any effect; it's in security-fix mode. For 2.7 go ahead. -- nosy: +georg.brandl ___ Python tracker ___ ___

[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-01 Thread Larry Hastings
Larry Hastings added the comment: Why shouldn't I check this in to the 2.7 / 3.1 branches? -- ___ Python tracker ___ ___ Python-bugs-

[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-01 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> needs patch versions: -Python 3.1, Python 3.4 ___ Python tracker ___ ___

[issue13086] Update howto/cporting.rst so it talks about 3.x instead of 3.0

2011-10-01 Thread Larry Hastings
New submission from Larry Hastings : 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 b