[Python-Dev] Multiprocessing maintenance
Hello everybody, Who is doing multiprocessing maintenance these days? I thought Ask Solem had been given commit privs for that, but I haven't seen any activity from him; and Jesse is, mostly, absent. Is anyone working on the multiprocessing issues? (no, I'm not planning to address them :-)) cheers Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] Exposing pkguitl's import emulation (was Re: r85538 - python/branches/py3k/Doc/library/pkgutil.rst)
On Sat, Oct 23, 2010 at 5:11 AM, Brett Cannon br...@python.org wrote: On Fri, Oct 22, 2010 at 09:26, Georg Brandl g.bra...@gmx.net wrote: Am 19.10.2010 17:24, schrieb P.J. Eby: Well, my intention at least was that they should be documented and released; it's the documenting part I didn't get around to. ;-) Of course, this was also pre-importlib; were we starting the work today, the obvious thing to do would be to expose the Python implementations of the relevant objects. I don't care much either way; however I don't really like when there are public APIs (i.e. non-underscore-prefixed globals in a non-underscore- prefixed module) that aren't documented, because it is confusing to developers who don't know if they can use it or not. (See re.scanner.) The best thing is probably to let Brett (Hello Brett!) determine how much of it can be replaced by importlib, and add a note to that effect to the pkgutil docs. The pkgutil stuff that was exposed cannot be directly replaced with a public API in Python 3.2, but the plan is that it will be in Python 3.3 when *all* concrete implementations of importers are exposed (because I will be attempting to bootstrap importlib). So if people are willing to wait and take me at my word that this will happen in Python 3.3, then this can come back out. But obviously I cannot make promises as Real Life will *actually* be starting for me when the Python 3.3 development cycle begins. Given the water under this bridge (and the fact PJE actually did intend for these to be public interfaces), I'm happy enough with the idea of having these pkgutil features documented properly. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Windows 64 build slave
On Wed, 13 Oct 2010 17:50:49 -0500 Brian Curtin brian.cur...@gmail.com wrote: [...] I have a Server 2008 R2 x64 box with the full Visual Studio that I could add to the buildbot fleet. It's a dual core with 4 GB of RAM, plenty of disk space, and it runs 24/7. The adventures of http://bugs.python.org/issue9778 show we would really benefit from a 64-bit Windows build slave. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Bug week-end on the 20th-21st?
Hello, The first 3.2 beta is scheduled by Georg for November 13th. What would you think of scheduling a bug week-end one week later, that is on November 20th and 21st? We would need enough core developers to be available on #python-dev. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Bug week-end on the 20th-21st?
Am 23.10.2010 19:08, schrieb Antoine Pitrou: Hello, The first 3.2 beta is scheduled by Georg for November 13th. What would you think of scheduling a bug week-end one week later, that is on November 20th and 21st? We would need enough core developers to be available on #python-dev. I'll be there. 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. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule
Am 22.10.2010 16:09, schrieb Benjamin Peterson: 2010/10/22 Dirkjan Ochtman dirk...@ochtman.nl: On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson benja...@python.org wrote: In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a tentative release schedule: November 13th - RC1 November 27th - RC2 December 11th - Final The last one might clash with the hg migration a bit, do we need to worry about that? Or did you purposely pick the day before the planned hg migration? I'm not too worried. Commits should be at a minimum, and changesets can be tagged post-transition if needed. I'm worried about build identification. Either the switchover happens before RC1, or after Final. I expect significant breakage from the Mercurial switchover, so that should all be figured out before or after the release. FWIW, I'm pondering to do all remaining 2.5 release from svn, despite the switchover to Mercurial, just so that the build identification does not get harmed. As a side note - I don't think two release candidates are really necessary. So if it helps, it may be reasonable to drop one of them. OTOH, I don't mind having two RCs, either. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Summary of Python tracker Issues
Issues stats: open2494 (+32) closed 19460 (+110) total 21954 (+56) The figures in parentheses look wrong. Last week, the stats said: No: they just mean something different that you think. +32 doesn't mean that there are now 32 more open issues than last week, but that 32 issue have been opened-and-not-closed in the week. You can see these 32 issues further down in the message. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Multiprocessing maintenance
Who is doing multiprocessing maintenance these days? I thought Ask Solem had been given commit privs for that, but I haven't seen any activity from him; and Jesse is, mostly, absent. Is anyone working on the multiprocessing issues? (no, I'm not planning to address them :-)) You mean: actively feeling responsible for it? I guess nobody - as for many other modules in the standard library. Or do you mean: who is willing to work on it, in principle? The last committers are georg.brandl, gregory.p.smith, martin.v.loewis, and antoine.pitrou. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Multiprocessing maintenance
You mean: actively feeling responsible for it? I guess nobody - as for many other modules in the standard library. Or do you mean: who is willing to work on it, in principle? Both. Originally the module is/was meant to be officially maintained by Jesse, as far as I understand. But bugs filed against multiprocessing have been lingering in the tracker for quite a long time. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule
2010/10/23 Martin v. Löwis mar...@v.loewis.de: I'm worried about build identification. Either the switchover happens before RC1, or after Final. I expect significant breakage from the Mercurial switchover, so that should all be figured out before or after the release. I hope that can be well tested before the release. FWIW, I'm pondering to do all remaining 2.5 release from svn, despite the switchover to Mercurial, just so that the build identification does not get harmed. As a side note - I don't think two release candidates are really necessary. So if it helps, it may be reasonable to drop one of them. OTOH, I don't mind having two RCs, either. I'm okay with dropping one RC, too. This should give us some wiggle room. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Multiprocessing maintenance
Both. Originally the module is/was meant to be officially maintained by Jesse, as far as I understand. But bugs filed against multiprocessing have been lingering in the tracker for quite a long time. I personally think we should treat these reports in the same way as all other lingering issues: explain to people that they need to submit patches if they want these issues fixed. Of course, this is then the same situation as with all the other patches that stay unreviewed (i.e. some get committed soon, some after some time, some never). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule
I will also do any future 2.6 release from svn. It does mean that patches for those release need to make it into svn. I propose that only the RM have commit to the svn branches after the switch. Sent from my digital lollipop. On Oct 23, 2010, at 2:03 PM, Martin v. Löwis mar...@v.loewis.de wrote: Am 22.10.2010 16:09, schrieb Benjamin Peterson: 2010/10/22 Dirkjan Ochtman dirk...@ochtman.nl: On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson benja...@python.org wrote: In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a tentative release schedule: November 13th - RC1 November 27th - RC2 December 11th - Final The last one might clash with the hg migration a bit, do we need to worry about that? Or did you purposely pick the day before the planned hg migration? I'm not too worried. Commits should be at a minimum, and changesets can be tagged post-transition if needed. I'm worried about build identification. Either the switchover happens before RC1, or after Final. I expect significant breakage from the Mercurial switchover, so that should all be figured out before or after the release. FWIW, I'm pondering to do all remaining 2.5 release from svn, despite the switchover to Mercurial, just so that the build identification does not get harmed. As a side note - I don't think two release candidates are really necessary. So if it helps, it may be reasonable to drop one of them. OTOH, I don't mind having two RCs, either. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/barry%40python.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule
Am 23.10.2010 20:56, schrieb Barry Warsaw: I will also do any future 2.6 release from svn. It does mean that patches for those release need to make it into svn. I propose that only the RM have commit to the svn branches after the switch. This is also my thinking. I would like to see a Mercurial branch for 2.5 established, and will then move any commits to it myself to the svn branch (there shouldn't be that many). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Goole Code-In Contest
Hello. I'm a student under 18 years, who really like programming in python. Few days ago I've found Google Code-In contesthttp://code.google.com/opensource/gci/2010-11/faqs.html, and I'm seriously considering it as a good opportunity do get more confident with Python. Although I've fixed a pair of bugs (see issue1100562 and issue9496), I'm still scared of breaking something and making silly things. So two days ago I've asked on #python-dev some infos about this contest, but nobody seemed to know if Python would have been a project in GCI, or give me any new information. Thanks to bitdancencer, I'm writing this mail, hoping some of you may consider this contest and give me the opportinity to be a better python developer. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
