Closed psychemedia closed 4 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
I do not see this problem. https://github.com/pypi/warehouse/issues/15611 suggests that this may happen when an outdated pkginfo
is installed. Can you check it you have the latest version of it and twine?
pkginfo
, twine
and hatchling
were all latest releases. Downgrading to hatchling==1.21.1
gives a build that twine
seems to be happy with.
Ah... seems like pkginfo
in was outdated in the env twine was calling from...
Using the template, a build seems to work fine, except for when I try to push to pypi with twine:
gives:
The
package.json
file hasname
andversion
both set.