I can do it but I don't want to be reviewing and accepting a PEP that's still under discussion, and I don't have the bandwidth to follow the discussion here -- I can only read the PEP. I will start that now. On Tue, Feb 24, 2015 at 1:03 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > On 24 February 2015 at 06:32, Paul Moore <p.f.moore at gmail.com> wrote: > > On 23 February 2015 at 19:47, Guido van Rossum <guido at python.org> wrote: > >> So is the PEP ready for pronouncement or should there be more > discussion? > > > > I think Brett's idea is worth incorporating, so let's thrash that out > first. > > > >> Also, do you have a BDFL-delegate or do you want me to review it? > > > > No-one has stepped up as BDFL-delegate, and there's no obvious > > candidate, so I think you're it, sorry :-) > > If Guido isn't keen, I'd be willing to cover it as the current runpy > module maintainer and the one that updated this part of the > interpreter startup sequence to handle the switch to importlib in 3.3. > > The PEP itself doesn't actually touch any of that internal machinery > though, it just makes the capability a bit more discoverable and > user-friendly. > > Regards, > Nick. > > -- > Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150224/191bb337/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4