-
Notifications
You must be signed in to change notification settings - Fork 414
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
Retrieve project version via setuptools_scm #4774
Comments
Some recipes use |
Thanks for the suggestion. It turns out that those GIT variables give a different version than setuptools_scm. Using the GIT variables in one of my projects, I get |
Would it work to allow conda build to pick up version information from the wheel or installed package after the build.sh scripts have run pip install? |
We don't use build.sh scripts nor do we run pip install. Having said that, why would that be a solution for this? Doesn't the current conda code that gets the version from setup.py do this before the wheel is created or the package installed? Our pyproject.toml creates a version.py file containing the version and this needs to be part of the conda package. |
Is there any update for this request? |
Checklist
What is the idea?
As is the case with the
load_setup_py_data
, the functionload_file_data
should be able to retrieve the version of the project via setuptools_scm.Why is this needed?
In pyproject.toml we rely on setuptools_scm to retrieve the version of the project. I have tried to use the new
load_file_data
function to load our project.toml file but Jinja doesn't retrieve the version via that file. We have followed the instructions here and here to set up project.toml but whatever I try,load_file_data
returns the literal string as defined inpyproject.toml
and doesn't call setuptools_scm to get the project version.What should happen?
It should be possible to use the directive
{% set data= load_file_data() %}
to retrieve the dynamically determined project version via setuptools_scm.Additional Context
No response
The text was updated successfully, but these errors were encountered: