Pipenv not setting PYTHONPATH

Question

I have the following structure

.
├── module1
│   ├── __init__.py
│   └── start.py
├── module2
│   ├── __init__.py
│   └── settings.py
└── Pipfile

cat module1/start.py

from module2.settings import VAR

if __name__ == '__main__':
    print(VAR)

cat module2/settings.py

VAR = 'foo'

If I try to run my program I get

pipenv shell
python module1/start.py

Traceback (most recent call last):
  File "module1/start.py", line 1, in <module>
    from module2.settings import VAR
ModuleNotFoundError: No module named 'module2'

or

pipenv run python module1/start.py

Traceback (most recent call last):
  File "module1/start.py", line 1, in <module>
    from module2.settings import VAR
ModuleNotFoundError: No module named 'module2'

Why doesn't pipenv set PYTHONPATH correctly ?

zzart · Accepted Answer · 2019-02-11 13:17:35Z

6

I realized I can use .env files to setup PYTHONPATH and make pipenv use it.

echo "PYTHONPATH=${PWD}" >> .env

edited Feb 11, 2019 at 13:17

answered Oct 25, 2018 at 11:11

zzart

11.6k5 gold badges56 silver badges47 bronze badges

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

1 Comment

givemesnacks Over a year ago

It's safer to use >>: echo "PYTHONPATH=${PWD}" >> .env

Collectives™ on Stack Overflow

Pipenv not setting PYTHONPATH

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related