You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2022. It is now read-only.
Currently minipip only handles the case of single tar.gz file without setup.py in it (ie upip-packages) on its own. All other cases get delegated to pip.
There can be cases, when package publisher wants to provide different content for different targets. For example, most dependencies and content Adafruit-Blinka currently are not relevant for MicroPython.
aivarannamaa
changed the title
Make sure the right file gets downloaded when distribution publishes several files per release
Make sure the right file gets downloaded when several files per release are published
May 22, 2021
Currently
minipip
only handles the case of singletar.gz
file without setup.py in it (ie upip-packages) on its own. All other cases get delegated topip
.There can be cases, when package publisher wants to provide different content for different targets. For example, most dependencies and content Adafruit-Blinka currently are not relevant for MicroPython.
I don't know whether someone has already used this approach, but according to PEP 425, the most natural thing to do is using separate wheels with
micropython
orcircuitpython
Python tag: https://www.python.org/dev/peps/pep-0425/#python-tag . Here is an experiment with this https://github.com/aivarannamaa/packaging_experiment.If the communities accept this approach, then make sure
minipip
supports it.The text was updated successfully, but these errors were encountered: