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 pip does not have means for overriding the value of implementation_name when filtering dependencies. In particular, --implementation option does not work for this. See pypa/pip#9981 for discussion.
I suppose this issue can't progress until pip starts supporting overriding markers. I could try patching sys.implementation.name, but even if it works with current version of pip, this hack is not guaranteed to work in the future.
The text was updated successfully, but these errors were encountered:
aivarannamaa
changed the title
Make sure correct dependencies are selected if implementation_name environment marker is used
Make sure correct dependencies are selected if implementation_name="micropython" environment marker is used
May 23, 2021
aivarannamaa
changed the title
Make sure correct dependencies are selected if implementation_name="micropython" environment marker is used
Make sure correct dependencies are selected if implementation_name environment marker is used
May 23, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
pip
does not have means for overriding the value ofimplementation_name
when filtering dependencies. In particular,--implementation
option does not work for this. See pypa/pip#9981 for discussion.I suppose this issue can't progress until
pip
starts supporting overriding markers. I could try patchingsys.implementation.name
, but even if it works with current version ofpip
, this hack is not guaranteed to work in the future.The text was updated successfully, but these errors were encountered: