[Python-Dev] PEPs shouldn't be considered docs
Brett Cannon
brett at python.org
Sat Oct 12 17:19:42 CEST 2013
More information about the Python-Dev mailing list
Sat Oct 12 17:19:42 CEST 2013
- Previous message: [Python-Dev] PEPs shouldn't be considered docs
- Next message: [Python-Dev] PEPs shouldn't be considered docs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Oct 12, 2013 at 5:38 AM, Paul Moore <p.f.moore at gmail.com> wrote: > On 12 October 2013 00:29, Nick Coghlan <ncoghlan at gmail.com> wrote: > > There's no grand policy change or clarification needed here, it's just > > another consequence of the fact that the import system isn't documented > > properly in versions prior to 3.3. > > And my personal apology for that. I knew when we wrote PEP 302 that it > needed proper documentation, but I couldn't find a good way to include > it in the docs and I couldn't face rewriting the import docs in a way > that would allow me to include it. > > Many thanks to Brett for ultimately doing it for me. > Actually thanks should go to Barry who rewrote the language ref docs for import. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20131012/2b0795ec/attachment.html>
- Previous message: [Python-Dev] PEPs shouldn't be considered docs
- Next message: [Python-Dev] PEPs shouldn't be considered docs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list