Peter Otten <__pete...@web.de> writes:
> Weird idea. Try putting the following in your __init__.py files:
>
> import pkgutil
> __path__ = pkgutil.extend_path(__path__, __name__)
> __path__.reverse()
> import __init__
> globals().update(vars(__init__))
> __path__.reverse()
That's rather astoundin
Ben Finney wrote:
> At this point I'm stuck. I can't see how to have the
> ‘docutils/__init__.py’ stop shadowing the names in the system-installed
> ‘docutils/__init__.py’, while still doing the namespace shuffle
> necessary to have my in-development module appear part of the wider
> package names
Howdy all,
With all the current fuss about namespace packages, I'm dealing with a
similar goal that I hope is possible with stock Python 2.x.
When developing a module intended to be part of an existing package
installed on the system, I want to write programs that will import the
*in-development*
