Matt Davis

@gitpushdashf I believe this is similar to another reported issue https://github.com/pypa/pipenv/issues/4967 that I believe will be fixed, or at least deterministic when the vendoring to pip 22.0.4 can be completed....

Please check with `pipenv==2022.4.20`

@gitpushdashf This may be solved by the nondeterminism in markers issue -- there is a branch out for it you could check: https://github.com/pypa/pipenv/pull/5373

@gitpushdashf marker determinism should be solved with `pipenv==2022.9.24`

@befeleme Your assessment makes sense to me, please feel free to open a PR for this.

This should be resolvable on `pipenv==2022.8.19` because we rely exclusively on the vendor'd pip which is the latest version `22.2.2` at the time of writing.

@Dzeri96 When I made the requirements.txt I got a more detailed error. Please see: ``` mdavis@Matts-MBP pipenv-4962 % cat requirements.txt numpy pandas riskfolio-lib==0.4.0 vectorbt==0.15.5 sanpy==0.8.12 asyncio aiohttp iso8601 ``` And...

> Pipenv doesn't produce an error message when it fails. @Dzeri96 Does it actually fail out, or just spin in locking or does it actually conclude for you in reasonable...

@delwaterman Your issue is more closely related to revised index restricted packages security feature. There are some threads that would be helpful to review: https://github.com/pypa/pipenv/issues/5053 https://github.com/pypa/pipenv/issues/5054

@Dzeri96 Please try again with `pipenv==2022.4.21`