pipenv: index restricted package cannot find sub-dependency when its index is non-default
When upgrading from 2022.3.28 to 2022.4.8, a pre-release package identified with ==x.y.z.alpha is no longer installing. I’m not using --pre or anything like that. Going back to 2022.3.28, it installs fine. Or rather, pipenv update --dev works fine.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 22 (13 by maintainers)
Commits related to this issue
- Work around for pipenv issue https://github.com/pypa/pipenv/issues/5042 — committed to pacificclimate/crmprtd by jameshiebert 2 years ago
- Upgrade PyCDS to 3.3.0 and fix CI Work around for pipenv issue https://github.com/pypa/pipenv/issues/5042 — committed to pacificclimate/crmprtd by jameshiebert 2 years ago
Ok, I am going to treat this as a question/request for support on the current behavior. If we want to improve the sub-dependency resolution of index restricted packages, then we need someone to write up an enhancement request/proposal that talks through a logical way to do that, or at least captures what the intended requirements are. Thanks!
@gitpushdashf hmmm I think that I may have introduced this regression with my changes here: https://github.com/pypa/pipenv/pull/5024/files
I will think more about it, please leave this issue opened.