On Dec 29, 2010, at 11:02 AM, Wichert Akkerman wrote: > On 12/29/10 16:45 , Michael Bayer wrote: >> Yeah this is what I'm seeing, that top level packagenames are used. I.e. >> I would just say, "Use sqlalchemycontrib as your package name, that's >> what everyone should use". It would appear this approach means nothing >> needs to happen at all witihin sqlalchemy core. > > I suspect you mean "use sqlalchemycontrib as your package namespace"? > Otherwise you will get 50 packages all called sqlalchemycontrib, which would > be a bit confusing :)
right the Python package is named <yourname>, but then right inside of it you have a package named "sqlalchemycontrib" which includes the namespace preamble which I guess in this terminology converts it from a "package" to a "package namespace". current questions: 1. confirm that one approach to allowing 3rd party packages is to encourage the usage of a common "package namespace" name. The core project itself doesn't use this name so no changes are required 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. one ancillary question: 3. is it possible some SQLA extension has already done this on their own regard ? http://pypi.python.org/pypi?%3Aaction=search&term=sqlalchemy&submit=search > > Wichert. > > -- > 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. > -- 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.
