pythonpath

I am structuring my Python application with the following folder architecture (roughly following the outline here ): myapp: myapp_service1: myapp_service1_start.py ... myapp_service2: myapp_service2_start.py ... myapp_service3: myapp_service3_start.py ... common: myapp_common1.py myapp_common2.py myapp_common3.py ... scripts: script1.py script2.py script3.py ... tests: ... docs: ... LICENSE.txt MANIFEST.in README This is ideal file/folder hierarchy for me, however, I am confused on how to reference modules from outside folders. For instance, myapp_service1_start.py needs to reference function

I am aware that, this question has been asked and answered many times. But, still i couldn't get rid of this. I found out the following info on my mac. cd /Library/Frameworks/Python.framework/Versions/ Current -> 2.7 3.6 whereispython /usr/bin/python which python /usr/bin/python which -a python /usr/bin/python /usr/bin/python python Python 2.7.10 (default) [GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.5)] on darwin Type "help", "copyright", "credits" or "license" for more information. Even though, when i edit ~/.bash_profile as below # Setting PATH for Python 2.7 # The original

I am trying to use pip to install a package locally in ~/.local . The problem is that the package (in an older version) is already available globally on the system. Even though the global python packages directory is not in my PYTHONPATH , pip still refuses to install, thinking that the package requirement is satisfied. This is similar to the issue described here, except I am not using sudo so the solution does not apply: pip - Requirement already satisfied? If I do: pip install --user numpy It says: Requirement already satisfied (use --upgrade to upgrade): numpy in /usr/local/lib/python2.7

I am struggling to add spark to my python path: (myenv)me@me /home/me$ set SPARK_HOME="/home/me/spark-1.2.1-bin-hadoop2.4" (myenv)me@me /home/me$ set PYTHONPATH=$PYTHONPATH:$SPARK_HOME:$SPARK_HOME/python:$SPARK_HOME/python/build:$SPARK_HOME/bin (myenv)me@me /home/me$ python -c 'import sys; print(sys.path)' ['', '/home/me/.virtualenvs/default/lib/python2.7', '/home/me/.virtualenvs/default/lib/python2.7/plat-x86_64-linux-gnu', '/home/me/.virtualenvs/default/lib/python2.7/lib-tk', '/home/me/.virtualenvs/default/lib/python2.7/lib-old', '/home/me/.virtualenvs/default/lib/python2.7/lib-dynload', '

I work on two servers, and on one server .pydistutils.cfg looks like: install_scripts=~/opt_old/bin install_data=~/opt_old/share install_lib=~/usr/lib/python2.6/site-packages I think, this creates problems with using pip and linking libraries on local versions of python. On the second server, the file is non existent, and I don't have any issues. Why do we need this file and why is PYTHONPATH not sufficient? I installed a local version of Python and renamed the file .pydistutils.cfg. Hence, it seems that the file is not that important. A pretty good write-up is here: http://bouktin.blogspot

The Yosemite (OS X 10.10) upgrade includes Python 2.7.6, and the process, as usual with Apple system updates, seems to completely replace the system packages directory, in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python This time, the process appears to have entirely omitted site.py . My understanding was that this file was essential to the functioning of Python , in particular, the proper construction of package search paths; but my Python (which uses nothing more than the Apple system Python and additional packages in site-packages ) works fine, and my paths remain

I'm on Mac OS X and I've heard that to avoid global installation of packages (using sudo) that might cause problems with the python files that OS X uses, the path to install python packages must be different than that of OS X. Currently python executables are installed in : /usr/local/bin/ Pip installs modules over here : /usr/local/lib/python2.7/site-packages Python is used from here : /usr/local/bin/python Are these paths safe? If you are on OS X, you should also have Python in /usr/bin : $ which -a python /usr/local/bin/python /usr/bin/python If you are using brew , the first python should