put dependency models into your main application, not the alembic directory.
the "env.py" file is loaded through a special per-file loader, so it isn't
really part of a Python "package" per se. the other things that env.py needs,
have them import from your normal application, e.g. "from myapp.
Having the same need, I'd like to know if there is a way to do this.
Thanks
On Thursday, November 14, 2013 4:24:40 AM UTC-5, Michal Nowikowski wrote:
>
> Hello,
>
> I observed that I repeat myself in upgrade modules.
> So I concluded that it would be good to put that code into separate python
>
