I\'m trying to use alembic which is an sqlalchemy tool in python. You type a command and it generates a folder \"alembic\" with py files inside. The py file inside, needs to lin
You have two possible solutions to your problem:
Add the path to apps catalogue by running following BASH / SH shell commands in your terminal:
$ export PYTHONPATH=$PYTHONPATH:'/path/to/apps'
Please not that adding it to the PATH environment variable won't work. To find out more about PYTHONPATH, how to manage it plus nice and friendly info on modules in general:
http://www.stereoplex.com/blog/understanding-imports-and-pythonpath
Please note however that this approach does affect your system's PYTHONPATH. It is highly recommended to use a virtualenv - just in case things go wrong, it won't affect all your system and other apps. When using virtualenvwrapper:
$ add2virtualenv '/path/to/apps'
More HERE.
Alternatively, you can do the same but just for a script runtime by adding:
import sys
sys.path.append('/path/to/apps')
to your apps/alembic/env.py
file.
Finally, in same file, make a following change:
from myapp.configs.config import DefaultConfig
And please note that your apps/myapp
folder should also contain __init__.py
file (might be empty) to make Python to treat is as a module as Demian Brecht pointed out.
Is myapp
a self-contained application, or a sub-application such as ones that you can find using Django? If it's a self-contained app, then you're kinda going about things wrong. What you really want to do is to install the dependencies that your app has in order to be able to access them without having to use relative imports and the like (which is bad practice, especially if anyone but you is using the app).
What you likely will want to do (again, if it's self-contained):
alembic
as a dependency: pip install alembic
requirements.txt
file: pip freeze > requirements.txt
Now, you should be able to use alembic via import alembic
from anywhere within your project.
Edit:
Your directory structure is also a little wonky. You'll want to put all of your app-specific modules into another myapp
subdirectory:
myapp
myapp
__init__.py
configs/__init__.py
The reason for this is so that you can add myapp
to your PYTHONPATH
and be able to import any modules from your app via from myapp import foo
. As it stands, if myapp
is on your PYTHONPATH
, you'll only be able to access the submodules from the second namespace level (i.e. import configs
), which is bad for obvious reasons.