you are running `manage.py` through `coverage` – a wrapper over a Python script. So the directory where that wrapper is located is added to `sys.path` instead of the current directory.
---
### Author:  [@Matthias84](https://travis-ci.community/u/Matthias84)
#### Post date: [August 12, 2019, 4:34pm UTC](https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/3 "2019-08-12T16:34:00Z")
Unfortunatly, this doesn’t seem to solve my problem 🙁
I added
> ```
> before_install:
> - export PYTHONPATH=$PYTHONPATH:$(pwd)
>
> ```
and checked the variable via echo. It looks good and includes the directory of my project. Also just invoking `python manage.py test` results in this issue …
I also tried to rollout the repo on another server to avoid bugs due local artifacts, but also on that server everything works fine.
Sorry, but any further ideas?
> **[GitHub - Matthias84/papersquirrel: read-it-later clone for easy selfhosting](https://github.com/Matthias84/papersquirrel)**
>
> read-it-later clone for easy selfhosting. Contribute to Matthias84/papersquirrel development by creating an account on GitHub.
---
### Author:  [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [August 12, 2019, 5:55pm UTC](https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/4 "2019-08-12T17:55:05Z")
Well, debugging is the further idea. It’s always the same:
- Identify the exact place in the code where the error manifests itself
- Examine the program’s state at that moment to find out which of the values is wrong
- Track the wrong value back to its origin
You can insert debug printing into files if you know how to do that on the fly, or [request debug mode for your project](https://docs.travis-ci.com/user/running-build-in-debug-mode/#enabling-debug-mode) and edit the code by hand or run it under debugger.
---
### Author:  [@Matthias84](https://travis-ci.community/u/Matthias84)
#### Post date: [August 17, 2019, 5:38am UTC](https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/5 "2019-08-17T05:38:37Z")
Well, 40+ builds later and trying different ideas, but I didn’t solved the problem yet and I’m close to give up 😭
First I just try to run only the testsuites itself, but n
All in all, this seems to be a problem with the [import path](https://docs.djangoproject.com/en/2.2/topics/settings/#designating-the-settings), but I checked, that the project root folder and the settings subfolder are on the paths:
```
$ echo $PATH
/home/travis/virtualenv/python3.6.7/bin:/home/travis/bin:/home/travis/.local/bin:/usr/local/lib/jvm/openjdk11/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v8.12.0/bin:/home/travis/.rvm/gems/ruby-2.5.3/bin:/home/travis/.rvm/gems/ruby-2.5.3@global/bin:/home/travis/.rvm/rubies/ruby-2.5.3/bin:/home/travis/gopath/bin:/home/travis/.gimme/versions/go1.11.1.linux.amd64/bin:/usr/local/maven-3.6.0/bin:/usr/local/cmake-3.12.4/bin:/usr/local/clang-7.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/travis/.rvm/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin:/home/travis/.yarn/bin:/home/travis/build/Matthias84/papersquirrel:/home/travis/virtualenv/python3.6.7/bin:/home/travis/bin:/home/travis/.local/bin:/usr/local/lib/jvm/openjdk11/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v8.12.0/bin:/home/travis/.rvm/gems/ruby-2.5.3/bin:/home/travis/.rvm/gems/ruby-2.5.3@global/bin:/home/travis/.rvm/rubies/ruby-2.5.3/bin:/home/travis/gopath/bin:/home/travis/.gimme/versions/go1.11.1.linux.amd64/bin:/usr/local/maven-3.6.0/bin:/usr/local/cmake-3.12.4/bin:/usr/local/clang-7.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/travis/.rvm/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin:/home/travis/.yarn/bin:/home/travis/build/Matthias84/papersquirrel:/home/travis/build/Matthias84/papersquirrel/papersquirrel/settings
python -c 'import sys; print(sys.path)'
['', '/home/travis/build/Matthias84/papersquirrel', '/home/travis/build/Matthias84/papersquirrel/papersquirrel/settings', '/home/travis/virtualenv/python3.6.7/lib/python36.zip', '/home/travis/virtualenv/python3.6.7/lib/python3.6', '/home/travis/virtualenv/python3.6.7/lib/python3.6/lib-dynload', '/opt/python/3.6.7/lib/python3.6', '/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages']
```
If I skip the `--settings`parameter, the suite runs as expected, but of course it doesn’t has the right settings to do it’s job.
I also tried different other approaches, that say it’s a problem of the travis virtualenv or to find my module itself:
- switch to `python3`
- invoke via `python -m`
- create **init**.py at root folder
- try only settings.ci instead
- rename project folder to uniqe name
Any help would be appreciated 😕
---
### Author:  [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [August 17, 2019, 10:15am UTC](https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/6 "2019-08-17T10:15:02Z")
[A check of file structure and `sys.path` at the time of import](https://travis-ci.org/native-api/papersquirrel/builds/573080606) shows…
… that the 2nd check was unnecessary. There’s no `./papersquirrel/settings/ci.py`. Apparently, you forgot to commit it…
* * *
Update: the link above is now dead. This is what I did there, roughly:
```auto
script:
- |-
python -m pdb <
c
import sys,os
os.system("ls -Rl")
p sys.path
c
q
!
```
---
### Author:  [@Matthias84](https://travis-ci.community/u/Matthias84)
#### Post date: [August 17, 2019, 8:00pm UTC](https://travis-ci.community/t/django-settings-modules-not-found-modulenotfounderror/4681/7 "2019-08-17T20:00:38Z")
God damnit, you are right! 🦸 My .gitignore blocked the settings file and my test on another server was with a custom local settings file …
Sometimes it’s the most basic things … thank you very much!