-
Notifications
You must be signed in to change notification settings - Fork 153
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
Remove metadata.json from the generated files in .dist-info #195
Comments
This should also resolve #75. |
PEP 426 is actually deferred, not rejected, so it doesn't hurt to have However, chances are that the format will actually change before (and if) it gets approved, so in that regard removing |
Whoops, I was using this dist-info json for various automation stuff and it all broke after wheel 0.31 release. What's the machine-readable replacement now? Do we have to parse that |
@wimglenn You can either use the
|
@di will give it a shot, thanks! |
For reference, Jfrog Artifactory relies on Workaround: downgrade wheel to 0.30.0 |
The latest version of wheel (0.32.1, just released) no longer writes the metadata.json file (see pypa/wheel#195). Instead, we must now read the version from the METADATA file. This change also tightens up the release docs a bit.
The latest version of wheel (0.32.1, just released) no longer writes the metadata.json file (see pypa/wheel#195). Instead, we must now read the version from the METADATA file. This change also tightens up the release docs a bit.
With newer Wheel releases, there is no more metadata.json file; the METADATA file should be used instead (see: pypa/wheel#195). This change updates our PyPI importer so that it uses the latter. * guix/import/pypi.scm (define-module): Remove unnecessary modules and export the PARSE-WHEEL-METADATA procedure. (parse-wheel-metadata): Add procedure. (guess-requirements): Use it. * tests/pypi.scm (test-metadata): Test it.
As PEP 426 was never accepted, I don't feel like we should generate this file anymore in the
.dist-info
directory in the wheel file.The text was updated successfully, but these errors were encountered: