Re: PEP 420: Implicit Namespace Packages

On 19 April 2012 21:18, Eric V. Smith <[email protected]> wrote:

> This reflects (I hope!) the discussions at PyCon. My plan is to produce
> an implementation based on the importlib code, and then flush out pieces
> of the PEP.
>
> In particular, I want to make sure the PEP addresses the various
> objections that were raised, especially by Nick.
>
>
So a namespace package is a directory (tree) on sys.path. For a standard
Python install how will these be installed?

If you need to install "foo.bar" and "foo.baz" will distutils and packaging
do the right thing? (And what specifically is the right thing for Python's
own package management tools - merging the namespace packages or keeping
them separate somehow?)

setuptools creates a new directory for each installed package and adds this
directory to sys.path using pth files. It's a bit of a hack, but it allows
namespace packages to co-exist.

Michael



> Eric.
>
> _______________________________________________
> Import-SIG mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/import-sig
>



-- 

http://www.voidspace.org.uk/

May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html

_______________________________________________
Import-SIG mailing list
[email protected]
http://mail.python.org/mailman/listinfo/import-sig