Re: [Python-Dev] Python 2.6.2 and 3.0.2

2009-03-14 Thread Martin v. Löwis
Jason R. Coombs wrote: > I'm still holding my breath for Python 2.6.2, which fixes a Windows > DLL linking issue that was already fixed in 3.0.1. Obviously, the > proposed schedule has passed, but I would prefer a release sooner > than later. I suggest you start breathing again. Martin _

Re: [Python-Dev] Python 2.6.2 and 3.0.2

2009-03-14 Thread Jason R. Coombs
I'm still holding my breath for Python 2.6.2, which fixes a Windows DLL linking issue that was already fixed in 3.0.1. Obviously, the proposed schedule has passed, but I would prefer a release sooner than later. Of course, that's just my preference. Regards, Jason > -BEGIN PGP SIGNED MESS

Re: [Python-Dev] Python 2.6.2 and 3.0.2

2009-02-18 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 18, 2009, at 1:49 AM, Brett Cannon wrote: If there are really enough fixes to warrant it, sure. Otherwise would it be worth more to just wait until after PyCon where there is a bigger chance of fixed issues? Good point. Barry -BEGI

Re: [Python-Dev] Python 2.6.2 and 3.0.2

2009-02-17 Thread Brett Cannon
On Tue, Feb 17, 2009 at 12:18, Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Thinking again about 3.0.2. > > If we'd like to do bug fix releases before Pycon, I suggest Monday March > 9th for code freeze and tagging. That would mean a Tuesday March 10th > release. > >

[Python-Dev] Python 2.6.2 and 3.0.2

2009-02-17 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thinking again about 3.0.2. If we'd like to do bug fix releases before Pycon, I suggest Monday March 9th for code freeze and tagging. That would mean a Tuesday March 10th release. What do you think? Barry -BEGIN PGP SIGNATURE- Version