Closed ZAdamMac closed 3 years ago
Upon further review it also appears that the .cfg file is also not being placed as would otherwise be expected. This is a critical bug that will prevent adoption in new users and can be limiting to (e.g.) recovering users hwho cannot access their old .cfg file.
This is down to the structure of the "default configuration" dictionary which is used to generate this configuration file. Commit 7284540 includes the relevant code change. Bug will stay open until the 2.1.1 release.
2.1.1 release is complete. Issue is resolved.
Describe the bug Tapestry does not currently correctly handle instances where it is invoked without a config file available.
To Reproduce Steps to reproduce the behavior:
tapestry.cfg
python3 -m tapestry
Expected behavior This should simply exit after the issue is raised rather than attempting to proceed, which is what is causing the error listed below.
Log/Console Output Where possible, add the output of the Logs or Console when the problem occurs.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.