-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
setuptools_scm does not create a version file after 8.0.0 release #960
Comments
The cli is no longer accidentally overwriting files Long term the intent is to put this into a build backend in general |
What should I do to make this file appear? |
Editable installation or building a wheel make it happen What's your use case? |
I actually use setuptools_scm not really for setuptools. |
In that case a opt in flag is needed |
Do I understand correctly that currently there is no such flag in setuptools_scm? |
correct, the way you use it was never a officially supported way before |
Truth be told I was very pleased with how setuptools_scm worked in this way. |
i understand the sentiment on the usage, but the behavior you used as a feature was a artifact of having to work around design issues in setuptools now that we have the use-case known explicitly, a proper command to write a version file can be added |
I just ran into this issue. I definitely would like to see this added as a cli command/argument. I often find myself wanting to make sure that my version.py file is updated but don't want to spend a long time fully building a wheel, when updating the version info is much faster. I was using |
pyproject.toml
The text was updated successfully, but these errors were encountered: