pythonpath | 易学教程

Best practice for reusing python code [closed]

阅读更多关于 Best practice for reusing python code [closed]

问题 I have write a python library app(which contains several *.py files). And several of my python projects need to reuse the code in the library app. What's the recommended best practice for reusing python code? Currently I have thought out three options: Copy and paste. This is far away from best practice. It violates the DRY principle.(Don't repeat yourself.) Add the folder of the library app to the environment variable PYTHONPATH: export PYTHONPATH=/path/to/library/app . Then every projects

Where to put a configuration file in Python?

阅读更多关于 Where to put a configuration file in Python?

问题 In development mode, I have the following directory tree : | my_project/ | setup.py | my_project/ | __init__.py | main.py | conf/ | myproject.conf I use ConfigParser to parse the myproject.conf file. In my code, it's easy to load the file with a good path : my_project/conf/myproject.conf The problem is : When I install my project using the setup.py, the configuration file are situated (thanks to setup.py) in the /etc/my_project/myproject.conf and my application in the /usr/lib/python<version>

Pyspark append executor environment variable

阅读更多关于 Pyspark append executor environment variable

Is it possible to append a value to the PYTHONPATH of a worker in spark? I know it is possible to go to each worker node, configure spark-env.sh file and do it, but I want a more flexible approach I am trying to use setExecutorEnv method, but with no success conf = SparkConf().setMaster("spark://192.168.10.11:7077")\ .setAppName(''myname')\ .set("spark.cassandra.connection.host", "192.168.10.11") / .setExecutorEnv('PYTHONPATH', '$PYTHONPATH:/custom_dir_that_I_want_to_append/') It creates a pythonpath env.variable on each executor, force it to be lower_case, and does not interprets $PYTHONPATH

Python : How to access file from different directory

阅读更多关于 Python : How to access file from different directory

问题 I have the following project structure SampleProject com python example source utils ConfigManager.py conf constants.cfg How to access constants.cfg from ConfigManager.py. I have a limitation I can not give full path(absolute path) of constants.cfg because if I run in different PC it should work with out any modification Also if I represent something like below, I can access the file. But I don't want to give back slash every time filename = ..\\..\\..\\..\\..\\..\\constants.cfg` Currently I

sys.path different in Jupyter and Python - how to import own modules in Jupyter?

阅读更多关于 sys.path different in Jupyter and Python - how to import own modules in Jupyter?

In Jupyter my own little module is not loaded but in python/bpython is everything is fine. When typing import sys print(sys.path) the path to my module will not in show in Jupyter but in python/bpython it is still there. I am using: PYTHONPATH in .bashrc to include my module, Jupyter and bpython inside a virtualenv. The most similar questions is this Cannot import modules in jupyter notebook; wrong sys.path How to configure Jupyter to load my modules automagically? Here is what I do on my projects in jupyter notebook, import sys sys.path.append("../") # go to parent dir from customFunctions

set pythonpath before import statements

阅读更多关于 set pythonpath before import statements

My code is: import scriptlib.abc import scriptlib.xyz def foo(): ... some operations but the scriptlib is in some other directory, so I will have to include that directory in environment variable "PYTHONPATH". Is there anyway in which I can first add the scriptlib directory in environment variable "PYTHONPATH" before import statement getting executed like : import sys sys.path.append('/mypath/scriptlib') import scriptlib.abc import scriptlib.xyz def foo(): ... some operations If so, is the value only for that command prompt or is it global ? Thanks in advance This will add a path to your

Effect of using sys.path.insert(0, path) and sys.path(append) when loading modules

阅读更多关于 Effect of using sys.path.insert(0, path) and sys.path(append) when loading modules

I was recently having a problem with a python ImportError, where the module was found when running on my local computer but not found on the CI server. I solved this problem by swapping sys.path.append(path) in my script with sys.path.insert(0, path) where path is the string module location. Since this is my module and not an installed package ( related question ), why does the order of paths fix this problem? Because python checks in the directories in sequential order starting at the first directory in sys.path list, till it find the .py file it was looking for. Ideally, the current

Python Pythonpath Modules install

阅读更多关于 Python Pythonpath Modules install

问题 I am kind of annoyed by the installation of modules in python and had a lot of trouble with it, so it would be fantastic to find a good solution for it. Here are my issues: PYTHONPATH: How can I tell easy_install/Python where to install my packages? Even though I put: /Library/Python/2.6/site-packages in my .bash_profile With: PYTHONPATH="/Library/Python/2.6/site-packages" export PYTHONPATH It wont import packages I have there. On the other site everything I put into: /Library/Frameworks

Why is my Python 'sys.path' different for each tool I use to run my code?

阅读更多关于 Why is my Python 'sys.path' different for each tool I use to run my code?

问题 I'm confused about the rules used to construct my Python sys.path . I understand that the fist entry will be "the directory containing the script that was used to invoke the Python interpreter", or an empty string if Python was invoked interactively, and that the last entires will be entries based on the installation of Python. But I'm confused about what's going on between these two sets of entries, in particular, how they relate to my PYTHONPATH. When I (A) execute a script that prints out

Python: select one of multiple installed module versions

阅读更多关于 Python: select one of multiple installed module versions

On my system, I have several modules installed multiple times. To give an example, numpy 1.6.1 is installed in the standard path at /usr/lib/python2.7/dist-packages , and I have an updated version of numpy 1.8.0 installed at /local/python/lib/python2.7/site-packages/ . The reason I cannot simply remove the old version is that I do not have permissions to change anything on my work computer. I however need to use the new numpy version. I have added /local/python/lib/python2.7/site-packages/ to my PYTHONPATH . Unfortunately, this does not help, since /usr/lib/python2.7/dist-packages is inserted