-
Notifications
You must be signed in to change notification settings - Fork 11
feat: add a Makefile goal simple-index
that generates a PEP-503 compatible Simple Index directory inside the dist
#947
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
base: main
Are you sure you want to change the base?
Conversation
…patible Simple Index directory inside the dist
Hmm, should we call the Makefile goal 🤷🏻♂️ |
@behnazh the generated <!-- https://peps.python.org/pep-0503/ -->
<!DOCTYPE html>
<html>
<head><meta name='pypi:repository-version' content='1.3'></head>
<body>
<a href='package-2.16.0-py3-none-any.whl'>package-2.16.0-py3-none-any.whl</a>
<a href='package-2.16.0.tar.gz'>package-2.16.0.tar.gz</a>
</body>
</html> does not make use of digest hashes as recommended in the specification:
We should probably add that and I think that would look something like this: <a href='package-2.16.0-py3-none-any.whl#sha256=82a57ea6a6ec2cea54501b4798dd4684b3666fde92ba1bb524f37791b1ef810b'>package-2.16.0-py3-none-any.whl</a>
<a href='package-2.16.0.tar.gz#sha256=f75bb93f5b3097a3c8f93c3bc4bc357fc17e1db266fd2de04dab76c236e247c9'>package-2.16.0.tar.gz</a> |
Thanks for this PR, it's great.
|
Can we test this feature somehow in |
Hmm… you mean to use the simple index 🤔 Probably if we would add a Docker file? Hmm… |
I don't think you would need to use a Docker file. You can test it in a separate |
As discussed with @behnazh this changes makes available a PEP-503 compatible Simple Repository directory inside of our dist/ directory.
We can now use
pip
and its--extra-index-url
argument to install packages, including support for their package hashes. For example to install the binary package (pip’s default):or the source package (purge the
pip
cache first!):or from the generated requirements file using package hashes:
Should we mention/document this in the README, or is the comment in the Makefile enough?