-
Notifications
You must be signed in to change notification settings - Fork 33
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
Path to the config.yml file #19
Comments
Yes, this is the expected behavior. In practice, I use an application's root directory as its working directory, and the template follows this convention. For development, the root directory is the project root (subdirectories are One advantage of doing things this way is that the runtime behavior is the same for an installed application as it is during development. Note that the tests also assume that the root directory is the working directory. You can replace the config path with an absolute directory if that fits your needs, but then you might have a mismatch between development and production. Also, you can always use |
Thank you very much for your explanation and for the template! |
When I install the app with
pip install -e .
and I call the cli from from any working directory other than the top directory oft the project, I get a file not found error:$ name_of_the_app -w DEBUG hello
If I run the same command from the top level directory of the app, the config.yml file loads.
OS: Win10
Python 3.11.3
Is this expected behaviour? Should I replace the relative default path
etc/config.yml
with an absolute path, for example one generated with the package platformdirs?The text was updated successfully, but these errors were encountered: