Avoid export PYTHONPATH every time for init.py to work

Question

`-- MyDir
|-- FolderA
|   |-- __init__.py
|   |-- ScriptA.py
`-- FolderB
    |-- __init__.py
    |-- ScriptB.py

The above is an example of my current structure. In both FolderA and FolderB, there are .from FolderX import * in __init__.py, X is A or B.

I want to run ScriptB.py which imports FolderA first: from FolderA import *. However, executing python ScriptB.py under FolderB reports ModuleNotFoundError: No module named 'FolderA';

My current workaround to get this work is typing export PYTHONPATH=/path/to/MyDir:$PYTHONPATH every time I start the conda environment. I would like to ask for the reason behind this and how could one avoid doing this way.

EDIT: it seems that I should have used Folder and Script to keep simplicity.

CristiFati · Accepted Answer · 2019-01-21 13:47:36Z

2

If PackageA and PacakgeB at the same directory level you can just add __init__.py in that directory too:

App
----__init__.py
----PackageA
---- ...
--------__init__.py
----PackageB
---- ...
--------__init__.py

Otherwise, if those packages are independently developed that you can install them as global packages.

edited Jan 21, 2019 at 13:47

CristiFati

41.5k9 gold badges68 silver badges114 bronze badges

answered Jan 21, 2019 at 13:42

ybl

1,63512 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Francis Over a year ago

I don't know if I understand it correctly, but simply adding __init__.py under MyDir doesn't work.

Felix · Accepted Answer · 2019-01-21 13:46:17Z

I can see a few ways to tackle this. First, I would consider the possibility of making them a single package. But that can be quickly discarded if they clearly are not.

If they truly are separate packages, you still have options. If one is ready to be released, you can surely install it to your Python environment via pip install using a setup.py script and all things associated with it. See Python packaging tutorial for more info.

Finally, and most likely you are still planning on modifying the contents. In that case pip has a very handy ability to install a package as a symbolic link. This way the package is read from the directory that you develop on. It is done by executing pip install -e . from the directory where setup.py exists. You can have a common setup script for "both" packages, using e.g. setuptools.find_packages. Or you can modify the folder structure slightly to have a different setup for each package. Now they are importable as normal Python packages.

emmet02 · Accepted Answer · 2019-01-21 14:38:33Z

0

Use conda develop

https://conda.io/docs/commands/build/conda-develop.html

This allows you to add a directory to a conda.pth file in site-packages of the environment of your choosing, which will be added to your pythonpath automatically.

conda develop ~/path/to/work_in_progress/code/ -n environment_name

answered Jan 21, 2019 at 14:38

emmet02

9425 silver badges8 bronze badges

Collectives™ on Stack Overflow

Avoid export PYTHONPATH every time for init.py to work

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related