-
Notifications
You must be signed in to change notification settings - Fork 123
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
Unfriendly error when the version can't be determined #445
Comments
Thanks for the report. The final error is "ValueError: Empty module name" It looks like the problem is not the version. To me it looks like, towncrier has no idea for which project/source it's supposed to work on. Towncrier is designed to be used by software developers. Have you reviewed the docs from https://towncrier.readthedocs.io/en/stable/quickstart.html ? From your
|
My config file is actually the first example from here: https://towncrier.readthedocs.io/en/stable/index.html#quick-start. In this example (and the project I'm considering to use towncrier in) there is no Python project, and you're supposed to supply the version number manually. |
True. Thanks for the details So the issue is something like this. If no version is found, towncrier fallbacks to detect the version via python auto-detections, but if Python project is not defined/found, it ends up with the Not sure how to fix it I guess that in I am leaving this report open and happy to review a fix for it :) Thanks again for the report |
Another option to fix this, is throwing more documentation into trying to fix this, and highlight that for non-python project, a version is required. There is room for improvements, we just need time for this :) |
It could just display the error message if |
Given this setup:
running
towncrier build
yields this error message:This in no way describes the actual problem, which is that towncrier couldn't determine the project version. It would be nice if it could display a friendlier message, e.g. "Unable to determine the project version. Use the --version option."
The text was updated successfully, but these errors were encountered: