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 tchrist
Recipients Arfrever, ezio.melotti, jkloth, mrabarnett, pitrou, r.david.murray, tchrist, terry.reedy
Date 2011-08-14.19:06:00
SpamBayes Score 3.3812842e-07
Marked as misclassified No
Message-id <12962.1313348749@chthon>
In-reply-to <1313344015.71.0.218551063153.issue12729@psf.upfronthosting.co.za>
Content
Ezio Melotti <report@bugs.python.org> wrote
   on Sun, 14 Aug 2011 17:46:55 -0000: 

>> I'm a bit confused on this.  You no longer fix bugs in Python 2?

> We do, but it's unlikely that we will introduce major changes in behavior.

> Even if we had to get rid of narrow builds and/or fix len(), we would
> probably only do it in the next 3.x version (i.e. 3.3), and not in the
> next bug fix release of 3.2 (i.e. 3.2.2).

Antoine Pitrou <report@bugs.python.org> wrote
   on Sun, 14 Aug 2011 17:36:42 -0000:

> This is even truer for stable branches, and Python 2 is very much a
> stable branch now (no more feature releases after 2.7).

Does that mean you now go to 2.7.1, 2.7.2, etc?

I had thought that 2.6 was going to be the last, but then 2.7
ame out.  I think I remember Guido said something about there 
never being a 2.10, so I wasn't too surprised to see 2.7.  

--tom
History
Date User Action Args
2011-08-14 19:06:01tchristsetrecipients: + tchrist, terry.reedy, pitrou, jkloth, ezio.melotti, mrabarnett, Arfrever, r.david.murray
2011-08-14 19:06:01tchristlinkissue12729 messages
2011-08-14 19:06:00tchristcreate