i have a few projects families with a model like this:
/shared_model/setup.py /shared_model/shared_model/ /shared_model/shared_model/sqlalchemy_api/.. /shared_model/shared_model/sqlalchemy_model/.. /shared_model/shared_model/utils/... /shared_model/tests_unit the sqlalchemy_model directory just has the objects and relationships as derived from declarative_base() and metadata. the `sqlalchemy_api` has some integrated model operations that are used in multiple projects. the various apps that use the library themselves will create an engine and call configure_mappers. the unit tests also create their own engine. i keep it that way, because the various frameworks I use have their own ways of specifying database connection details. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/c712fa85-ebe6-4b8f-a125-d426ff5dcd69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
