I suggest putting trivial “launcher” scripts at the top level of your project, and making each of the subproject folders into packages. The modules in the packages can import each other or common code can be factored out into a common package. Here’s what the structure would look like, if we assume the various merger … Read more
This is not recommended, as it hard-codes a path and makes it difficult to run the script elsewhere, but you can do >>> import sys >>> sys.path.insert(0,’/home/anand/’) >>> print(sys.path) [‘/home/anand/’, ”, ‘/usr/local/lib/python2.7/dist-packages/_pdbpp_path_hack’, ‘/usr/local/lib/python2.7/dist-packages/goose-0.0.1-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/jieba-0.33-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/cssselect-0.9.1-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/nanoservice-0.1.5-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/nanomsg-1.0a2-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/msgpack_python-0.4.2-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/DecisionTree-2.2.5-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/nudepy-0.2-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/wsgilog-0.3-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/distribute-0.7.3-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/PIL-1.1.7-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/MySQL_python-1.2.5-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/munkres-1.0.7-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/parsedatetime-1.4-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/argparse-1.3.0-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/tusker-0.1-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/SQLAlchemy-1.0.3-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/numpy-1.9.2-py2.7-linux-x86_64.egg’, ‘/usr/local/lib/python2.7/dist-packages/turkic-0.2.5-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/scikits.bootstrap-0.3.2-py2.7.egg’, ‘/usr/local/lib/python2.7/dist-packages/pyvision-0.1-py2.7-linux-x86_64.egg’, ‘/home/anand/playspace/languages/python_pkgs/ets’, ‘/usr/local/lib/python2.7/dist-packages/Scrapy-1.1.0dev1-py2.7.egg’, … Read more
I’m quite a beginner in Python and I found the answer of Anand was very good but quite complicated to me, so I try to reformulate : 1) insert and append methods are not specific to sys.path and as in other languages they add an item into a list or array and : * append(item) … Read more
I had the same error, and this fix my issue python -m pip install django 🙂 Done!
Allow me to propose a fourth alternative: take the time to learn how to package your library and install it in your site-packages; it’s easier than one may think and I’m convinced it’s time well spent. This is a very good starting point: https://packaging.python.org/en/latest/
I’m not sure there’s a perfect solution for this, but in the interest of being explicit rather than implicit (PEP 20), I’ve decided to check in a file that needs to be sourced before running any script. This is one extra manual step but you can put this in a Makefile for instance. env.sh export … Read more
Probably, pip installs packages into dist-packages directory, which is not included into PYTHONPATH environment variable. You have a couple of solutions: Create and configure virtualenv for your project, before using pip. This is the most Pythonic way Try to install Django using built-in pip module: python -m pip install django This command should install packages … Read more
You can add custom paths this way. Go to File->Settings->project Interpreter In the Project-Interpreter field, click the down facing arrow and select “show All” In that Menu, highlight your interpreter and then in the right menu, select the button “Show paths for the selected interpreter” (this is the last button) click the plus symbol to … Read more
PYTHONPATH is somewhat of a hack as far as package management is concerned. A “pretty” solution would be to package your library and install it. This could sound more tricky than it is, so let me show you how it works. Let us assume your “package” has a single file named wow.py and you keep … Read more
I found two answers to my question in the Anaconda forum: 1.) Put the modules into into site-packages, i.e. the directory $HOME/path/to/anaconda/lib/pythonX.X/site-packages which is always on sys.path. This should also work by creating a symbolic link. 2.) Add a .pth file to the directory $HOME/path/to/anaconda/lib/pythonX.X/site-packages. This can be named anything (it just must end with … Read more