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.
On Dec 29, 2010, at 1:24 AM, Hong Minhee wrote: > In case of Flask and Sphinx, they use names like flaskext and sphinxcontrib > (no period). > > https://bitbucket.org/birkenfeld/sphinx-contrib/ > http://flask.pocoo.org/docs/extensiondev/ > > I would suggest that SQLAlchemy uses sqlalchemycontrib or sqlalchemyext (or > any other?) for extension namespace if we cannot use sqlalchemy.contrib. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > 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 sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
