-
Notifications
You must be signed in to change notification settings - Fork 489
Fix to enable loading from current directory #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1 similar comment
|
There should probably be a test added that fails with current master but is fixed by this change. |
|
@RazerM You're right, I added such a test. |
|
Oops I'm sorry, I made a mistake, I'm investigating it. |
|
This is an important correction. It would be nice to have this merged back in. |
|
@pvmm I thought so too, as the issue it fixes has been reported at least twice, but this PR has received zero attention from the maintainers since I opened it almost two months ago. |
|
Bumping this issue as its pretty important |
|
❤️ Merged in! Thanks everyone! |
* Fix to enable loading from current directory * Add test to make sure loading from current dir works * Reorder test_core tests to avoid directory problem * Reorder curr dir test again, and use os.chdir
This is a fix for #108, which is due I believe to the fact that
find_dotenvdoes not go back far enough in the call stack to find the calling module, which causes its path searching starting point to be itself (i.e.main.py).@theskumar, @RazerM