You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So for the reasons previously described it would be good to have a way in environs to force a failure if the specified env file does not exist, by e.g. checking the return code from dotenv and raising an exception if it is false.
The text was updated successfully, but these errors were encountered:
#311 modifies env.read_env to return False if the file is not found. This allows users to handle that case as they see fit, e.g. raise an exception, log a warning.
Previously discussed in #199
See theskumar/python-dotenv#297
It looks like now there is https://github.com/theskumar/python-dotenv/pull/388/files which will cause load_dotenv to return false if no vars were read:
So for the reasons previously described it would be good to have a way in environs to force a failure if the specified env file does not exist, by e.g. checking the return code from dotenv and raising an exception if it is false.
The text was updated successfully, but these errors were encountered: