-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Building using a pyproject.toml
results in version being 0.0.0.0
#636
Comments
At first glance likely a issue with setuptools versions, Im not sure when I can debug more, but as a first item update setuptools_scm and setuptools with pip and try again |
@WhyNotHugo it seems that by switching to build you resolved the issue, can i close? |
I encounter the same issue with the latest setuptools and setuptools_scm. |
I have the same issue, project repo at the exact commit. It seems even Here's my environment
|
Ill geht to this this afternoon, i believe it may require setuptools newer than 52 as well as setuptools_scm master |
Here's some data: It seems one really needs |
I can also reproduce the issue with the latest versions of pip, wheel, setuptools and setuptools-scm |
Basically setup.py has no way of getting the deps Never invoke setup. Py, always use build or pip The docs should recommend a stock setup.py that errors better |
Should I open a new issue for the |
Hitting the same issue. Followed the docs; version is
Curiously:
I can of course fix this by
Pip Upgrading to latest pip
I do get correct version returned from Adding Any suggestions? |
Solved. There was a typo in my ... Next issue. This code ☝️ obviously breaks on this (by all documented means, legitimate) config:
Removing |
closing as unplanned, my understanding is that the initial issue is resolved a number of other comments are either new issues (that i will not create) or configuration mistakes i will create extra cards for failing on custom describe commands that are outside of what can be handled |
For posterity (and sorry for grave digging, but I was hitting this with What I was seeing:
As you can see, both the name and version weren't there! 😭 My Setup
[build-system]
requires = ["setuptools>=62.6", "setuptools_scm[toml]>=6.2"]
build-backend = "setuptools.build_meta"
[project]
name = "pkgname"
dynamic = ["version", "dependencies"]
[tool.setuptools.dynamic]
dependencies = {file = ["requirements.txt"]}
[tool.setuptools_scm]
root = ".."
setup(
...,
include_package_data=True,
) My SolutionI had From #487 (comment), remember to have your Here were a few possible fixes I came across. Fixing
Fixing
How I fixed both:
I am not sure how to have
I don't believe this is correct. The And in other news, |
If trying to install this package in an offline manner (see also: linien-org/linien#378 ), the metadata pip will put for this installation might be 0.0.0, due to potential compatiblitiy issues with setuptools on the target host (RedPitaya probably). See also: pypa/setuptools-scm#636
I'm using a
pyproject.toml
that's pretty much like the example in the documentation.My relevant setup.cfg and setup.py.
When I run
python setup.py dist
, the resulting wheel has version 0.0.0. If I usepython -m build
, the version is correct (e.g.: it's determined based on the git-tag as expected).Is using
setup.py sdist
no longer supported, or is there something wrong with my setup?The text was updated successfully, but these errors were encountered: