On Wed, Dec 29, 2010 at 11:47 AM, Michael Bayer <[email protected]> wrote: > current questions: > > 2. what are the pros/cons to the the two approaches: common package > namespace named externally to the project, embedding a package namespace in > the project itself. Obviously the former seems better to me since the > "sqlalchemy." namespace remains unaffected.
afaik, you would have to forfeit sqlalchemy/__init__.py with the latter, which would be very disruptive. With namespace packages, you have no guarantee on which package's __init__.py is used. Quoting http://packages.python.org/distribute/setuptools.html#namespace-packages You must NOT include any other code and data in a namespace package’s __init__.py. Even though it may appear to work during development, or when projects are installed as .egg files, it will not work when the projects are installed using “system” packaging tools – in such cases the __init__.py files will not be installed, let alone executed. -Ron -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
