On Oct 12, 2013, at 11:19 AM, Brett Cannon wrote:
>Actually thanks should go to Barry who rewrote the language ref docs for
>import.
I can actually say it was fun due to all the great work on importlib. :)
-Barry
___
Python-Dev mailing list
Python-Dev@
On 12 Oct 2013 19:38, "Paul Moore" wrote:
>
> On 12 October 2013 00:29, Nick Coghlan 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 pers
On Sat, Oct 12, 2013 at 5:38 AM, Paul Moore wrote:
> On 12 October 2013 00:29, Nick Coghlan 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
On 12 October 2013 00:29, Nick Coghlan 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
On 11 Oct 2013 21:25, "Ned Batchelder" wrote:
>
> I wanted to teach a co-worker about "from __future__ import
absolute_import" today, so I thought I'd point them at the docs. The page
for "__future__" starts with a bunch of internal details that almost no one
needs to know. There's a table at th
On 10/11/2013 04:24 AM, Ned Batchelder wrote:
I'd like to suggest that we not consider PEPs to be documentation.
+1
The few times I've tried to use the PEPs to understand current Python it was
confusing, wrong, and a waste of time.
--
~Ethan~
___
On Oct 11, 2013, at 07:24 AM, Ned Batchelder wrote:
>I'd like to suggest that we not consider PEPs to be documentation.
Absolutely +1. That was never the intention behind PEPs.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.pyth
2013/10/11 Ned Batchelder :
> I wanted to teach a co-worker about "from __future__ import absolute_import"
> today, so I thought I'd point them at the docs. The page for "__future__"
> starts with a bunch of internal details that almost no one needs to know.
> There's a table at the end that menti
I wanted to teach a co-worker about "from __future__ import
absolute_import" today, so I thought I'd point them at the docs. The
page for "__future__" starts with a bunch of internal details that
almost no one needs to know. There's a table at the end that mentions
the actual importable names,
