Closed mgorny closed 1 year ago
@mgorny I used hatch to build and publish based on the config https://github.com/sigmavirus24/github3.py/pull/1144 If I don't do that, PyPI blocks the publish, so I do not have a clear solution for the problem for now.
To be honest, I don't think there's a good solution right now, except for not using dot in project name. Good news is, to the best of my knowledge normalization treats .
, _
and -
as equivalent, so if you named the project e.g. github3-py
this shouldn't break anything depending on it (but please don't take my word on it).
To be honest, I don't think there's a good solution right now, except for not using dot in project name. Good news is, to the best of my knowledge normalization treats
.
,_
and-
as equivalent, so if you named the project e.g.github3-py
this shouldn't break anything depending on it (but please don't take my word on it).
I'll go back about 10 years in time and rename it right away
https://github.com/sigmavirus24/github3.py/pull/1142#issuecomment-1520707331
The nonconformant/"invalid" artifact names predate the latest release:
@mgorny we have now 4.0.1
Thanks. I'll test it tomorrow early morning, if that's ok.
It works fine. Thanks again!
The PyPI artifacts for 4.0.0 violate the current version of sdist & wheel specifications by using dots in filenames:
However, the directory inside sdist seems to be named correctly:
FWIK hatchling does the correct thing so I guess the release pipeline is broken somewhere and renames the files to non-conformant filenames (but leaving the internal structure correct).