Re: [Python-Dev] Multiprocessing maintenance
On Sat, Oct 23, 2010 at 2:20 PM, Antoine Pitrou wrote: > >> 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. Like Ask said, we both are, and still feel responsible. Finding time is another problem altogether, and it's been in short supply. In short: No, neither one of us has walked away. jesse ___ Python-Dev mailing list [email protected] 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
On Sat, Oct 23, 2010 at 2:10 PM, "Martin v. Löwis" wrote: >> 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. Both Ask and myself feel actively responsible. Antoine could have just as easily asked privately. ___ Python-Dev mailing list [email protected] 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. FWIW, I'm +1, and I'll try to get the Sao Paulo users group to participate. rbp -- http://isnomore.net ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Change to logging Formatters: support for alternative format styles
I've just checked in a change to logging into the py3k branch (r85835),
including doc changes and tests, for providing slightly more flexibility in
alternative format styles for logging.
Basically, Formatter.__init__ gets an extra optional keyword arg style=. This is then used to merge the format string with
the LogRecord: either fmt % record.__dict__, or fmt.format(**record.dict), or
string.Template(fmt).substitute(**record.dict). Backward compatibility is
maintained (unless I've missed something).
This does not cater for how you combine the logging message + its args when you
make a logging call, but should work with any existing library which uses
%-formatting in its logging calls.
We discussed this here around a year ago in the context of generally encouraging
a move from %-formatting to {}-formatting, but there seemed to be no obvious
easy path forward.
As of now, and even without this change I've just checked in, developers can use
{}- or $-formatting in their logging messages using e.g.
logger.debug(__('Message with {} {}', 2, 'place-holders'))
with a suitable class standing in for __. A bit ugly, I know, with extra
parentheses and what not, but hopefully for those who must have {} now it
shouldn't be too much of a price to pay and there's no major performance
implication, as actual rendering to string is done as late as possible, just as
it is now.
Comments welcome. Assuming there are no strong objections asking for reversion
of this change, I'll publicise to the wider community in a few days.
Regards,
Vinay Sajip
___
Python-Dev mailing list
[email protected]
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?
On Sat, Oct 23, 2010 at 1:08 PM, Antoine Pitrou wrote: > > 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. If anyone wants to spin up local, in person presences for this - namely, small local sprints, let me / the sprints team know. We (The PSF) have money to help fund. This would be the perfect use of the resources - more info http://pythonsprints.com/ jesse ___ Python-Dev mailing list [email protected] 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?
On Mon, 25 Oct 2010 12:22:24 -0200, Rodrigo Bernardo Pimentel wrote: >> Am 23.10.2010 19:08, schrieb Antoine Pitrou: >>> 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. > >FWIW, I'm +1, and I'll try to get the Sao Paulo users group to participate. I think this is a great idea (both Antoine's initial suggestion and the idea of getting users groups to participate). I'll be around and able to participate that weekend except for evening US Eastern time. -- R. David Murray www.bitdance.com ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r85839 - python/branches/py3k/Python/sysmodule.c
On Mon, 25 Oct 2010 19:37:23 +0200 (CEST) victor.stinner wrote: > > -if (argc == 0) > -return; > argv0 = argv[0]; Well, are you sure argv[0] is valid when argc is 0? Regards Antoine. ___ Python-Dev mailing list [email protected] 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?
On Mon, 25 Oct 2010 11:32:42 -0400 "R. David Murray" wrote: > On Mon, 25 Oct 2010 12:22:24 -0200, Rodrigo Bernardo Pimentel > wrote: > >> Am 23.10.2010 19:08, schrieb Antoine Pitrou: > >>> 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. > > > >FWIW, I'm +1, and I'll try to get the Sao Paulo users group to participate. > > I think this is a great idea (both Antoine's initial suggestion and the > idea of getting users groups to participate). > > I'll be around and able to participate that weekend except for evening > US Eastern time. Ok, so 20th-21st of November it shall be! Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Python bug week-end : 20-21 November
Hello, The development team of the Python interpreter (a.k.a python-dev) is organizing a bug week-end on Saturday 20th and Sunday 21st of November. We would like to encourage anyone who feels interested in participating to give it a try. Contributing to Python is much less intimidating than it sounds. You don't need to have previous experience with modifying the Python source; in fact bug days offer a good opportunity to learn the basics by asking questions and working on relatively simple bugs (see "how to get prepared" below). And most core developers are actual human beings! How it happens -- The bug week-end will happen on the #python-dev IRC channel on the Freenode network, where several core developers routinely hang out. No physical meeting is scheduled as far as I know, but anyone is encouraged to organize one and announce it on the official Python channels such as this one. Participants (you!) join #python-dev and collaboratively go through the Python issue tracker at http://bugs.python.org . From there, you can provide patches and/or review existing patches. Also, you can help us assess issues on any specific topic you have expertise in (the range of topics touched in the stdlib is quite broad and it is more than likely that the core developers' expertise is lacking in some of them). Or, if you feel shy, you can simply watch other people work and slowly get more confident about participating yourself. Development is public and lurkers are welcome. What you can work on - Our expectation is that Python 3.2 beta 1 will have been released a couple of days before the bug week-end and, therefore, one primary goal is to polish the 3.2 branch for the following betas and the final release. There are many issues to choose from on the bug tracker; any bug fixes or documentation improvements will do. New features are discouraged: they can't be checked in before the official 3.2 release. How to get prepared --- If you are a beginner with the Python codebase, you may want to read the development guide available here (courtesy of Brian Curtin): http://docs.pythonsprints.com/core_development/beginners.html There's a small practical guide to bug days/week-ends on the wiki: http://wiki.python.org/moin/PythonBugDay And the development FAQ holds answers to generic development questions: http://www.python.org/dev/faq/ You can also do all of the above during the bug week-end, of course. Please, don't hesitate to ask us questions on the #python-dev channel. Regards Antoine. ___ Python-Dev mailing list [email protected] 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
On Mon, 25 Oct 2010 10:01:43 -0400 Jesse Noller wrote: > On Sat, Oct 23, 2010 at 2:10 PM, "Martin v. Löwis" wrote: > >> 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. > > Both Ask and myself feel actively responsible. Antoine could have just > as easily asked privately. Well, the question and its eventual answer were meant for public consumption, not for my personal edification. Thanks for answering anyway. We can then continue to put you and Ask in the nosy lists for multiprocessing issues. Regards Antoine. ___ Python-Dev mailing list [email protected] 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
On Mon, Oct 25, 2010 at 7:19 PM, Antoine Pitrou wrote: > On Mon, 25 Oct 2010 10:01:43 -0400 > Jesse Noller wrote: >> On Sat, Oct 23, 2010 at 2:10 PM, "Martin v. Löwis" >> wrote: >> >> 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. >> >> Both Ask and myself feel actively responsible. Antoine could have just >> as easily asked privately. > > Well, the question and its eventual answer were meant for public > consumption, not for my personal edification. > Thanks for answering anyway. We can then continue to put you and Ask in > the nosy lists for multiprocessing issues. > > Regards > > Antoine. I'm not pleased with the current state of affairs and I am working to change this. I apologize for the delay on the bugs. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] PyCon 2011 Reminder: Call for Proposals, Posters and Tutorials - us.pycon.org
PyCon 2011 Reminder: Call for Proposals, Posters and Tutorials - us.pycon.org === Well, it's October 25th! The leaves have turned and the deadline for submitting main-conference talk proposals expires in 7 days (November 1st, 2010)! We are currently accepting main conference talk proposals: http://us.pycon.org/2011/speaker/proposals/ Tutorial Proposals: http://us.pycon.org/2011/speaker/proposals/tutorials/ Poster Proposals: http://us.pycon.org/2011/speaker/posters/cfp/ PyCon 2011 will be held March 9th through the 17th, 2011 in Atlanta, Georgia. (Home of some of the best southern food you can possibly find on Earth!) The PyCon conference days will be March 11-13, preceded by two tutorial days (March 9-10), and followed by four days of development sprints (March 14-17). We are also proud to announce that we have booked our first Keynote speaker - Hilary Mason, her bio: "Hilary is the lead scientist at bit.ly, where she is finding sense in vast data sets. She is a former computer science professor with a background in machine learning and data mining, has published numerous academic papers, and regularly releases code on her personal site, http://www.hilarymason.com/. She has discovered two new species, loves to bake cookies, and asks way too many questions." We're really looking forward to having her this year as a keynote speaker! Remember, we've also added an "Extreme" talk track this year - no introduction, no fluff - only the pure technical meat! For more information on "Extreme Talks" see: http://us.pycon.org/2011/speaker/extreme/ We look forward to seeing you in Atlanta! Please also note - registration for PyCon 2011 will also be capped at a maximum of 1,500 delegates, including speakers. When registration opens (soon), you're going to want to make sure you register early! Speakers with accepted talks will have a guaranteed slot. We have published all registration prices online at: http://us.pycon.org/2011/tickets/ Important Dates November 1st, 2010: Talk proposals due. December 15th, 2010: Acceptance emails sent. January 19th, 2011: Early bird registration closes. March 9-10th, 2011: Tutorial days at PyCon. March 11-13th, 2011: PyCon main conference. March 14-17th, 2011: PyCon sprints days. Contact Emails: Van Lindberg (Conference Chair) - [email protected] Jesse Noller (Co-Chair) - [email protected] PyCon Organizers list: [email protected] ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Issue 10194 - Adding a gc.remap() function
I have a patch that adds a new function to the gc module. The gc.remap() function uses the tp_traverse mechanism to find all references to any keys in a provided mapping, and remaps these references in-place to instead point to the value corresponding to each key. The motivation for adding this method is to enable writing a module that provide an enhanced version of imp.reload. The builtin reload function is very useful for iterating on a single module within the Python interpreter shell, but in more complex situations it very limited. In particular, instances of classes declared in the reloaded module will continue to reference the old versions of the classes, and other modules that imported elements of the old module using the 'from ... import ...' syntax will continue to refer to the stale version of the functions or classes that they imported. The gc.remap() function enables writing a new version of reload which uses imp.reload to reload a module and then replaces all references to stale objects from the old module to instead point to equivalent newly defined objects. This still has many limitations, for instance if an __init__ function has been changed the new __init__ will not be run on old instances. On the other hand, in many cases this is sufficient to continue iterating on code without needing to restart the Python environment, which can be a significant time savings. I initially tried to implement this reloading strategy entirely in Python using gc.getreferrers() to find references to objects defined in the old module, but I found it was too difficult to reliably replace references in objects once they had been found. Since the GC already has a way to find all fields that refer to objects, it seemed fairly straightforward to extend that mechanism to additionally modify references. This reloading strategy is documented in more detail here: http://doublestar.org/in-place-python-reloading/ A potentially controversial aspect of this change is that the signature of the visitproc has been modified to take (PyObject **) as an argument instead of (PyObject *) so that a visitor can modify fields visited with Py_VISIT. A few traverse functions in the standard library also had to be changed to use Py_VISIT on the actual members rather than on aliased pointers. I also have a prototype of an enhanced reload function using gc.remap. This is only a partial implementation of the proposal, in particular it does not rehash dictionaries that have been invalidated as a result of reloading, and it does not support custom __reload__ hooks. A link to the code as well as some examples are here: http://doublestar.org/python-hot-loading-prototype/ Please let me know if you have any feedback on the reloading proposal, the hot loading prototype, or on the patch. Thanks, Peter ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
