On Wed, Jul 13, 2011 at 1:41 PM, Brett Cannon wrote:
> So are you claiming that the import of 'package' w/o the __future__
> statement actually succeeds even though there is no package.subpackage
> module? Obviously that would be a flat-out bug, but I just double-checked my
> sanity and that does
On Fri, Jul 8, 2011 at 06:51, Sylvain Thénault
wrote:
> Hi there,
>
> the documentation state that absolute_import feature is the default
> behaviour with python 2.7, though it seems that it behave differently
> with the __future__ import :
>
> $ cat package/__init__.py
>
> import subpackage
>
> $
Am 12.07.2011 15:30, schrieb Éric Araujo:
>> changeset: 71283:3a4b983dd70b
>> user:Georg Brandl
>> summary:
>> Fix syntax in packaging docs and update suspicious ignore file.
>>
>> files:
>> Doc/library/packaging.compiler.rst | 2 +-
>> Doc/packaging/builtdist.rst |
> changeset: 71283:3a4b983dd70b
> user:Georg Brandl
> summary:
> Fix syntax in packaging docs and update suspicious ignore file.
>
> files:
> Doc/library/packaging.compiler.rst | 2 +-
> Doc/packaging/builtdist.rst | 2 +-
> Doc/packaging/commandref.rst |
