From benjamin at python.org Sun Jun 6 02:14:44 2010 From: benjamin at python.org (Benjamin Peterson) Date: Sat, 5 Jun 2010 19:14:44 -0500 Subject: [python-committers] trunk frozen Message-ID: I'm now releasing 2.7rc1, so please no commits. -- Regards, Benjamin From benjamin at python.org Sun Jun 6 04:31:06 2010 From: benjamin at python.org (Benjamin Peterson) Date: Sat, 5 Jun 2010 21:31:06 -0500 Subject: [python-committers] trunk is open, but! Message-ID: Python 2.7 release candidate 1 has been released. That means the trunk is open, but we are also now in the final development phase for Python 2.7. Stability is the top priority now. Please be very careful about what you change now, ensuring that your alterations will not have unexpected consequences. Extra reviews are great. Definitely no new features. Let's usher 2.x out with style. Regards, Benjamin From michael at voidspace.org.uk Mon Jun 7 14:56:08 2010 From: michael at voidspace.org.uk (Michael Foord) Date: Mon, 07 Jun 2010 13:56:08 +0100 Subject: [python-committers] EuroPython Language Summit Message-ID: <4C0CEC68.8060006@voidspace.org.uk> Hello all, (Copied to python-committers in case I miss anyone.) I'm doing some more planning on the EuroPython language summit and you are invited but haven't yet told me if you can come or not. Either that or you have told me and I haven't recorded it properly and would appreciate being reminded (my apologies if this is the case). Please reply to this email at your earliest convenience. Confirmed attendees include Guido, Brett Cannon, myself, Georg Brandl, Amaury Forgeot D'Arc, M.-A. Lemburg, Antonio Cuni, Armin Rigo, Kristjan Jonsson, and Mark Dickinson. It will be a good time and a great opportunity to discuss the development of Python. The summit itself is in Birmingham UK on Sunday 18th July. http://www.europython.eu/ All the best, Michael Foord -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (?BOGUS AGREEMENTS?) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. From benjamin at python.org Sun Jun 20 06:31:42 2010 From: benjamin at python.org (Benjamin Peterson) Date: Sat, 19 Jun 2010 23:31:42 -0500 Subject: [python-committers] release candidate Message-ID: I apologize for silently missing 2.7rc2 today; an event ran longer than I anticipated. I plan to release tomorrow, Sunday. -- Regards, Benjamin From benjamin at python.org Mon Jun 21 17:56:02 2010 From: benjamin at python.org (Benjamin Peterson) Date: Mon, 21 Jun 2010 10:56:02 -0500 Subject: [python-committers] tagging 2.7rc2 Message-ID: So please no trunk commits! -- Regards, Benjamin From benjamin at python.org Mon Jun 21 19:16:52 2010 From: benjamin at python.org (Benjamin Peterson) Date: Mon, 21 Jun 2010 12:16:52 -0500 Subject: [python-committers] trunk open Message-ID: The final release is next, so there really should be excellent reasons to change things in the trunk now. -- Regards, Benjamin From g.brandl at gmx.net Sun Jun 27 11:17:24 2010 From: g.brandl at gmx.net (Georg Brandl) Date: Sun, 27 Jun 2010 11:17:24 +0200 Subject: [python-committers] Delaying 3.2 release Message-ID: Hi, I'm delaying the 3.2 alpha1 release by one week; I don't have enough time to sort through all the possible issues and get acquainted with the release machinery this weekend. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. From martin at v.loewis.de Sun Jun 27 19:07:35 2010 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Sun, 27 Jun 2010 19:07:35 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: Message-ID: <4C278557.8070807@v.loewis.de> > I'm delaying the 3.2 alpha1 release by one week; I don't have enough time > to sort through all the possible issues and get acquainted with the release > machinery this weekend. Should we perhaps delay the entire schedule by one month? A number of things that people want for 3.2 haven't happened yet. Not sure whether a month would help, of course. However, I wouldn't want to migrate to Mercurial between beta releases, for example. The release process probably needs several rounds to adjust to Mercurial, and we aren't even close to switching. Regards, Martin From brett at python.org Sun Jun 27 22:58:10 2010 From: brett at python.org (Brett Cannon) Date: Sun, 27 Jun 2010 13:58:10 -0700 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C278557.8070807@v.loewis.de> References: <4C278557.8070807@v.loewis.de> Message-ID: On Sun, Jun 27, 2010 at 10:07, "Martin v. L?wis" wrote: >> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >> to sort through all the possible issues and get acquainted with the release >> machinery this weekend. > > Should we perhaps delay the entire schedule by one month? A number of > things that people want for 3.2 haven't happened yet. Not sure whether > a month would help, of course. However, I wouldn't want to migrate to > Mercurial between beta releases, for example. The release process > probably needs several rounds to adjust to Mercurial, and we aren't even > close to switching. > Unless some long-term release of some major OS or distro is about to come out and was hoping to include 3.2 (and I don't think any are), I see no harm in postponing. I know I won't mind as I have some additions/deprecations in importlib that are landing in 3.2. From mal at egenix.com Mon Jun 28 13:17:55 2010 From: mal at egenix.com (M.-A. Lemburg) Date: Mon, 28 Jun 2010 13:17:55 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C278557.8070807@v.loewis.de> References: <4C278557.8070807@v.loewis.de> Message-ID: <4C2884E3.1040304@egenix.com> "Martin v. L?wis" wrote: >> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >> to sort through all the possible issues and get acquainted with the release >> machinery this weekend. > > Should we perhaps delay the entire schedule by one month? A number of > things that people want for 3.2 haven't happened yet. +1 > Not sure whether > a month would help, of course. However, I wouldn't want to migrate to > Mercurial between beta releases, for example. The release process > probably needs several rounds to adjust to Mercurial, and we aren't even > close to switching. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 28 2010) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2010-07-19: EuroPython 2010, Birmingham, UK 20 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From ziade.tarek at gmail.com Mon Jun 28 13:39:58 2010 From: ziade.tarek at gmail.com (=?ISO-8859-1?Q?Tarek_Ziad=E9?=) Date: Mon, 28 Jun 2010 13:39:58 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C2884E3.1040304@egenix.com> References: <4C278557.8070807@v.loewis.de> <4C2884E3.1040304@egenix.com> Message-ID: On Mon, Jun 28, 2010 at 1:17 PM, M.-A. Lemburg wrote: > "Martin v. L?wis" wrote: >>> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >>> to sort through all the possible issues and get acquainted with the release >>> machinery this weekend. >> >> Should we perhaps delay the entire schedule by one month? A number of >> things that people want for 3.2 haven't happened yet. > > +1 +1 From victor.stinner at haypocalc.com Mon Jun 28 13:41:24 2010 From: victor.stinner at haypocalc.com (Victor Stinner) Date: Mon, 28 Jun 2010 13:41:24 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: Message-ID: <201006281341.25510.victor.stinner@haypocalc.com> Le dimanche 27 juin 2010 11:17:24, Georg Brandl a ?crit : > I'm delaying the 3.2 alpha1 release by one week; I don't have enough time > to sort through all the possible issues and get acquainted with the release > machinery this weekend. For the 3.2 final, I would like to mark this issue has a blocker: http://bugs.python.org/issue8611 It's not possible to install Python in a non-ASCII directory (eg. user directory, user with a non-ASCII character in its name) on Windows. I think that nobody noticed this bug before because there are few early adopters (people testing Python3). I think that #8988 is a duplicate. Fix #8611 is not trivial. I opened ~20 issues to prepare the work. It's not finished yet. Victor From ncoghlan at gmail.com Mon Jun 28 14:21:48 2010 From: ncoghlan at gmail.com (Nick Coghlan) Date: Mon, 28 Jun 2010 22:21:48 +1000 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <201006281341.25510.victor.stinner@haypocalc.com> References: <201006281341.25510.victor.stinner@haypocalc.com> Message-ID: On Mon, Jun 28, 2010 at 9:41 PM, Victor Stinner wrote: > Le dimanche 27 juin 2010 11:17:24, Georg Brandl a ?crit : >> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >> to sort through all the possible issues and get acquainted with the release >> machinery this weekend. > > For the 3.2 final, I would like to mark this issue has a blocker: > > ? ?http://bugs.python.org/issue8611 > I went ahead and marked it as such - the RM reviews the open release blockers anyway before deciding whether or not to make a release, and will either demote them permanently (i.e disagree with the assessment of their importance), defer them (more common for alpha releases than later ones) or delay the release. We don't want to go crazy with it (the RM shouldn't be getting deluged with trivial issues to review all the time), but if you think something really should be a release blocker, feel free to bump the priority yourself. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia From barry at python.org Mon Jun 28 15:02:49 2010 From: barry at python.org (Barry Warsaw) Date: Mon, 28 Jun 2010 09:02:49 -0400 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> Message-ID: <20100628090249.0293208f@heresy> On Jun 27, 2010, at 01:58 PM, Brett Cannon wrote: >On Sun, Jun 27, 2010 at 10:07, "Martin v. L?wis" wrote: >>> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >>> to sort through all the possible issues and get acquainted with the release >>> machinery this weekend. >> >> Should we perhaps delay the entire schedule by one month? A number of >> things that people want for 3.2 haven't happened yet. Not sure whether >> a month would help, of course. However, I wouldn't want to migrate to >> Mercurial between beta releases, for example. The release process >> probably needs several rounds to adjust to Mercurial, and we aren't even >> close to switching. >> > >Unless some long-term release of some major OS or distro is about to >come out and was hoping to include 3.2 (and I don't think any are), I >see no harm in postponing. I know I won't mind as I have some >additions/deprecations in importlib that are landing in 3.2. As it currently stands the next version of Ubuntu, due out in October, will not include Python 3.2. The version after that is due in April, but will be open soon after the October release. Generally, I think it's a good idea to get major new toolchain packages in as early in the cycle as possible, and I'd like to get us on Python 3.2, if we're talking a 3.2b1 by mid October (instead of mid-Sept), with a final release in January, we should be fine I think. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From jnoller at gmail.com Mon Jun 28 16:40:58 2010 From: jnoller at gmail.com (Jesse Noller) Date: Mon, 28 Jun 2010 10:40:58 -0400 Subject: [python-committers] Xs Message-ID: From jnoller at gmail.com Mon Jun 28 19:31:38 2010 From: jnoller at gmail.com (Jesse Noller) Date: Mon, 28 Jun 2010 13:31:38 -0400 Subject: [python-committers] Xs In-Reply-To: References: Message-ID: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> My apologies everyone. Apparently my three year old knows how to work the mail app on my iPhone. On Jun 28, 2010, at 10:40 AM, Jesse Noller wrote: > From orsenthil at gmail.com Mon Jun 28 19:33:28 2010 From: orsenthil at gmail.com (Senthil Kumaran) Date: Mon, 28 Jun 2010 23:03:28 +0530 Subject: [python-committers] Xs In-Reply-To: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> References: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> Message-ID: <20100628173328.GD10019@remy> On Mon, Jun 28, 2010 at 01:31:38PM -0400, Jesse Noller wrote: > My apologies everyone. Apparently my three year old knows how to > work the mail app on my iPhone. Wow!. The youngest Python Core developer. :) -- Senthil If a guru falls in the forest with no one to hear him, was he really a guru at all? -- Strange de Jim, "The Metasexuals" From fdrake at acm.org Mon Jun 28 19:44:21 2010 From: fdrake at acm.org (Fred Drake) Date: Mon, 28 Jun 2010 13:44:21 -0400 Subject: [python-committers] Xs In-Reply-To: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> References: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> Message-ID: On Mon, Jun 28, 2010 at 1:31 PM, Jesse Noller wrote: > Apparently my three year old knows how to work the mail app on my iPhone. Dang! Already tainted by closed-source technologies... -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein From raymond.hettinger at gmail.com Mon Jun 28 20:02:28 2010 From: raymond.hettinger at gmail.com (Raymond Hettinger) Date: Mon, 28 Jun 2010 11:02:28 -0700 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C2884E3.1040304@egenix.com> References: <4C278557.8070807@v.loewis.de> <4C2884E3.1040304@egenix.com> Message-ID: <64CBB32D-6F31-4FFE-B95C-32BB4682ECA0@gmail.com> On Jun 28, 2010, at 4:17 AM, M.-A. Lemburg wrote: > "Martin v. L?wis" wrote: >>> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >>> to sort through all the possible issues and get acquainted with the release >>> machinery this weekend. >> >> Should we perhaps delay the entire schedule by one month? A number of >> things that people want for 3.2 haven't happened yet. > > +1 +1 Raymond From senn at maya.com Mon Jun 28 19:55:16 2010 From: senn at maya.com (Jeff Senn) Date: Mon, 28 Jun 2010 13:55:16 -0400 Subject: [python-committers] Xs In-Reply-To: References: <6B9F411F-D145-4A8D-B392-20C3D6B7F215@gmail.com> Message-ID: On Jun 28, 2010, at 1:44 PM, Fred Drake wrote: > On Mon, Jun 28, 2010 at 1:31 PM, Jesse Noller wrote: >> Apparently my three year old knows how to work the mail app on my iPhone. > > Dang! Already tainted by closed-source technologies... Are you referring to the iPhone mail app? Or the three-year-old? :-) From solipsis at pitrou.net Mon Jun 28 23:30:11 2010 From: solipsis at pitrou.net (Antoine Pitrou) Date: Mon, 28 Jun 2010 23:30:11 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C278557.8070807@v.loewis.de> References: <4C278557.8070807@v.loewis.de> Message-ID: <1277760611.3270.0.camel@localhost.localdomain> Le dimanche 27 juin 2010 ? 19:07 +0200, "Martin v. L?wis" a ?crit : > > I'm delaying the 3.2 alpha1 release by one week; I don't have enough time > > to sort through all the possible issues and get acquainted with the release > > machinery this weekend. > > Should we perhaps delay the entire schedule by one month? A number of > things that people want for 3.2 haven't happened yet. For the record, what are those things? From martin at v.loewis.de Mon Jun 28 23:58:35 2010 From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=) Date: Mon, 28 Jun 2010 23:58:35 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <1277760611.3270.0.camel@localhost.localdomain> References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> Message-ID: <4C291B0B.3020303@v.loewis.de> Am 28.06.2010 23:30, schrieb Antoine Pitrou: > Le dimanche 27 juin 2010 ? 19:07 +0200, "Martin v. L?wis" a ?crit : >>> I'm delaying the 3.2 alpha1 release by one week; I don't have enough time >>> to sort through all the possible issues and get acquainted with the release >>> machinery this weekend. >> >> Should we perhaps delay the entire schedule by one month? A number of >> things that people want for 3.2 haven't happened yet. > > For the record, what are those things? The ones I want to get done are PEPs 382 and 384. Something I know others want to achieve is the switch to Mercurial. A number of PEPs are targetted for 3.2 with unclear status: 3143, 3144, 3145, 3148. Regards, Martin From orsenthil at gmail.com Tue Jun 29 05:32:27 2010 From: orsenthil at gmail.com (Senthil Kumaran) Date: Tue, 29 Jun 2010 09:02:27 +0530 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C291B0B.3020303@v.loewis.de> References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> Message-ID: On Tue, Jun 29, 2010 at 3:28 AM, "Martin v. L?wis" wrote: > > The ones I want to get done are PEPs 382 and 384. Just to have the direct information on these PEPs inline. PEP 382 - Namespace Packages http://www.python.org/dev/peps/pep-0382/ PEP 383 - Definition of Stable ABI http://www.python.org/dev/peps/pep-0384/ > Something I know others want to achieve is the switch to Mercurial. A > number of PEPs are targetted for 3.2 with unclear status: 3143, 3144, > 3145, 3148. PEP 3143 - Standard Deamon Process Library http://www.python.org/dev/peps/pep-3143/ PEP 3144 - IP Address Manipulation Library http://www.python.org/dev/peps/pep-3144/ PEP 3145 - Asynchronous I/O for Subprocess.Popen http://www.python.org/dev/peps/pep-3145/ PEP 3148 - futures package http://www.python.org/dev/peps/pep-3148/ Except for the 'futures' package which featured discussion again recently, others have been in a sleeping mode for a while. There is a codeline ( I assume, it is stable) for the above mentioned additions to stdlib maintained outside the svn tree. -- Senthil From barry at python.org Tue Jun 29 15:12:40 2010 From: barry at python.org (Barry Warsaw) Date: Tue, 29 Jun 2010 09:12:40 -0400 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <4C291B0B.3020303@v.loewis.de> References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> Message-ID: <20100629091240.041b3505@heresy> On Jun 28, 2010, at 11:58 PM, Martin v. L?wis wrote: >The ones I want to get done are PEPs 382 and 384. I'd like to help with these. I remember we had a long thread a few weeks back about PEP 382 (namespace packages) and there are some tricky issues to work out. I need to go back and re-read that thread. Maybe Jason and Eric want to set up another local sprint to attack it again. >Something I know others want to achieve is the switch to Mercurial. A >number of PEPs are targetted for 3.2 with unclear status: 3143, 3144, >3145, 3148. I really think we need to make the switch to Mercurial as soon as 2.7 final is out. It's been long enough. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From dirkjan at ochtman.nl Tue Jun 29 15:24:39 2010 From: dirkjan at ochtman.nl (Dirkjan Ochtman) Date: Tue, 29 Jun 2010 15:24:39 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <20100629091240.041b3505@heresy> References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> <20100629091240.041b3505@heresy> Message-ID: On Tue, Jun 29, 2010 at 15:12, Barry Warsaw wrote: > I really think we need to make the switch to Mercurial as soon as 2.7 final is > out. ?It's been long enough. I got back into working on it last week (using a branch map to clean up all the feature branches we're going to shed for the conversion), but then it turned out that there is a regression in hgsubversion right now for r21112. It probably has something to do with the fact that this revision was manufactured by cvs2svn. Additionally, I've been stressing out quite a bit about my master's thesis, which is due in about 4 weeks. So I'm unlikely to spend much time on this during the rest of July, but would be quite happy to get back into it in August. Also, help would be appreciated with the hgsubversion regression; I can supply a complete traceback. Cheers, Dirkjan From brett at python.org Tue Jun 29 20:21:22 2010 From: brett at python.org (Brett Cannon) Date: Tue, 29 Jun 2010 11:21:22 -0700 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> <20100629091240.041b3505@heresy> Message-ID: On Tue, Jun 29, 2010 at 06:24, Dirkjan Ochtman wrote: > On Tue, Jun 29, 2010 at 15:12, Barry Warsaw wrote: >> I really think we need to make the switch to Mercurial as soon as 2.7 final is >> out. ?It's been long enough. > > I got back into working on it last week (using a branch map to clean > up all the feature branches we're going to shed for the conversion), > but then it turned out that there is a regression in hgsubversion > right now for r21112. It probably has something to do with the fact > that this revision was manufactured by cvs2svn. > > Additionally, I've been stressing out quite a bit about my master's > thesis, which is due in about 4 weeks. I'm working on my Ph.D. thesis right now, so I can relate. > So I'm unlikely to spend much > time on this during the rest of July, but would be quite happy to get > back into it in August. > > Also, help would be appreciated with the hgsubversion regression; I > can supply a complete traceback. Can you open a bug on bitbucket for it and post the link here? Since I am in the same boat as you I can't take a look at it myself, but lowering the barrier to trying to tackle should help raise the chances someone has a look. -Brett > > Cheers, > > Dirkjan > _______________________________________________ > python-committers mailing list > python-committers at python.org > http://mail.python.org/mailman/listinfo/python-committers > From brett at python.org Tue Jun 29 20:21:22 2010 From: brett at python.org (Brett Cannon) Date: Tue, 29 Jun 2010 11:21:22 -0700 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> <20100629091240.041b3505@heresy> Message-ID: On Tue, Jun 29, 2010 at 06:24, Dirkjan Ochtman wrote: > On Tue, Jun 29, 2010 at 15:12, Barry Warsaw wrote: >> I really think we need to make the switch to Mercurial as soon as 2.7 final is >> out. ?It's been long enough. > > I got back into working on it last week (using a branch map to clean > up all the feature branches we're going to shed for the conversion), > but then it turned out that there is a regression in hgsubversion > right now for r21112. It probably has something to do with the fact > that this revision was manufactured by cvs2svn. > > Additionally, I've been stressing out quite a bit about my master's > thesis, which is due in about 4 weeks. I'm working on my Ph.D. thesis right now, so I can relate. > So I'm unlikely to spend much > time on this during the rest of July, but would be quite happy to get > back into it in August. > > Also, help would be appreciated with the hgsubversion regression; I > can supply a complete traceback. Can you open a bug on bitbucket for it and post the link here? Since I am in the same boat as you I can't take a look at it myself, but lowering the barrier to trying to tackle should help raise the chances someone has a look. -Brett > > Cheers, > > Dirkjan > _______________________________________________ > python-committers mailing list > python-committers at python.org > http://mail.python.org/mailman/listinfo/python-committers > From martin at v.loewis.de Tue Jun 29 22:56:10 2010 From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 29 Jun 2010 22:56:10 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: <20100629091240.041b3505@heresy> References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> <20100629091240.041b3505@heresy> Message-ID: <4C2A5DEA.2040205@v.loewis.de> >> The ones I want to get done are PEPs 382 and 384. > > I'd like to help with these. I remember we had a long thread a few weeks back > about PEP 382 (namespace packages) and there are some tricky issues to work > out. I need to go back and re-read that thread. Maybe Jason and Eric want to > set up another local sprint to attack it again. Help is surely appreciated (but please do keep me involved). >> Something I know others want to achieve is the switch to Mercurial. A >> number of PEPs are targetted for 3.2 with unclear status: 3143, 3144, >> 3145, 3148. > > I really think we need to make the switch to Mercurial as soon as 2.7 final is > out. It's been long enough. I think this really needs a volunteer or more to contribute. I doubt anybody is working on the remaining issues. I still think we absolutely need to have a test installation that is completely ready with no known issues, up for at least 14 days. So if you want to switch to hg a week after 2.7 gets released, you would have had to bring up that test installation up last weekend. I don't want to find us in a situation were work is blocked or significantly more difficult just because some significant pieces of infrastructure were not in place when we made the switch. Regards, Martin From victor.stinner at haypocalc.com Wed Jun 30 10:02:11 2010 From: victor.stinner at haypocalc.com (Victor Stinner) Date: Wed, 30 Jun 2010 10:02:11 +0200 Subject: [python-committers] Delaying 3.2 release Message-ID: <201006301002.11203.victor.stinner@haypocalc.com> Le lundi 28 juin 2010 14:21:48, vous avez ?crit : > > For the 3.2 final, I would like to mark this issue has a blocker: > > > > http://bugs.python.org/issue8611 > > I went ahead and marked it as such - the RM reviews the open release > blockers anyway before deciding whether or not to make a release, and > will either demote them permanently (i.e disagree with the assessment > of their importance), defer them (more common for alpha releases than > later ones) or delay the release. Ok to mark it as a blocker, but it should only be a blocker for the 3.2 final, not the alpha releases. My initial patch is really huge: I cannot review it myself :-) I'm rewriting it from scratch to implement the "right" solution. Eg. My next patch will be on import to use the PyUnicodeObject* type instead of char*. I will open an issue for each patch. -- Victor Stinner http://www.haypocalc.com/ From g.brandl at gmx.net Wed Jun 30 10:43:57 2010 From: g.brandl at gmx.net (Georg Brandl) Date: Wed, 30 Jun 2010 10:43:57 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> Message-ID: Am 29.06.2010 05:32, schrieb Senthil Kumaran: > On Tue, Jun 29, 2010 at 3:28 AM, "Martin v. L?wis" wrote: >> >> The ones I want to get done are PEPs 382 and 384. > > Just to have the direct information on these PEPs inline. > > PEP 382 - Namespace Packages > http://www.python.org/dev/peps/pep-0382/ > PEP 383 - Definition of Stable ABI > http://www.python.org/dev/peps/pep-0384/ PEP 382 would be nice to have. >> Something I know others want to achieve is the switch to Mercurial. A >> number of PEPs are targetted for 3.2 with unclear status: 3143, 3144, >> 3145, 3148. > > PEP 3143 - Standard Deamon Process Library > http://www.python.org/dev/peps/pep-3143/ > > PEP 3144 - IP Address Manipulation Library > http://www.python.org/dev/peps/pep-3144/ > > PEP 3145 - Asynchronous I/O for Subprocess.Popen > http://www.python.org/dev/peps/pep-3145/ > > PEP 3148 - futures package > http://www.python.org/dev/peps/pep-3148/ > > Except for the 'futures' package which featured discussion again > recently, others have been in a sleeping mode for a while. > There is a codeline ( I assume, it is stable) for the above mentioned > additions to stdlib maintained outside the svn tree. All of these will need to be "finished" and proposed for inclusion officially, before they can be approved. All in all, hearing the arguments in this thread I agree that a month more time for development is a good thing, and I will update the release schedule accordingly. Georg From benjamin at python.org Wed Jun 30 16:43:09 2010 From: benjamin at python.org (Benjamin Peterson) Date: Wed, 30 Jun 2010 09:43:09 -0500 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> Message-ID: 2010/6/30 Georg Brandl : > All in all, hearing the arguments in this thread I agree that a month > more time for development is a good thing, and I will update the release > schedule accordingly. You could just throw in another alpha. It never hurts to get the code out there IMO. -- Regards, Benjamin From solipsis at pitrou.net Wed Jun 30 18:34:55 2010 From: solipsis at pitrou.net (Antoine Pitrou) Date: Wed, 30 Jun 2010 18:34:55 +0200 Subject: [python-committers] Delaying 3.2 release In-Reply-To: References: <4C278557.8070807@v.loewis.de> <1277760611.3270.0.camel@localhost.localdomain> <4C291B0B.3020303@v.loewis.de> Message-ID: <1277915695.3180.1.camel@localhost.localdomain> Le mercredi 30 juin 2010 ? 09:43 -0500, Benjamin Peterson a ?crit : > 2010/6/30 Georg Brandl : > > All in all, hearing the arguments in this thread I agree that a month > > more time for development is a good thing, and I will update the release > > schedule accordingly. > > You could just throw in another alpha. It never hurts to get the code > out there IMO. +1.