On Tue, Apr 19, 2011 at 10:57 AM, Nick Coghlan <[email protected]> wrote: > On Tue, Apr 19, 2011 at 3:06 PM, Stefan Behnel <[email protected]> wrote: >> I think this social problem of the PEP can only be solved if the CPython >> project stops doing the major share of the stdlib maintenance, thus freeing >> its own developer capacities to focus on CPython related improvements and >> optimisations, just like the other implementations currently do. I'm not >> sure we want that at this point. > > We've made a start on that aspect by granting CPython access to > several of the core developers on the other VMs. The idea being that > they can update the pure Python versions of modules directly rather > than having to wait for one of us to do it on their behalf. > > Of course, as Maciej pointed out, that is currently hindered by the > fact that the other VMs aren't targeting 3.3 yet, and that's where the > main CPython development is happening.
We're also slightly hindered by the fact that not all of us got privilages so far (Antonio Cuni in particular). > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/fijall%40gmail.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
