With certain sets of listed packages, the markers for numpy change back and forth on repeated runs of pipenv lock.
In our workflow, this issue caused problems when attempting to verify whether or not pipenv lock was run recently and seeing "different behavior on different machines", where the "different behavior" was just running pipenv lock a second time and seeing different output.
Expected result
Running pipenv lock a second time immediately should not make any additional changes to Pipfile.lock.
Actual result
some lines in Pipfile.lock flip between
"markers": "python_version >= '3.8'",
and
"markers": "python_version < '3.10'",
with each successive pipenv lock. 3.7 is also sometimes seen.
Issue description
This appears to be a re-occurrence of https://github.com/pypa/pipenv/issues/4660.
With certain sets of listed packages, the
markersfornumpychange back and forth on repeated runs ofpipenv lock.In our workflow, this issue caused problems when attempting to verify whether or not
pipenv lockwas run recently and seeing "different behavior on different machines", where the "different behavior" was just runningpipenv locka second time and seeing different output.Expected result
Running
pipenv locka second time immediately should not make any additional changes toPipfile.lock.Actual result
some lines in
Pipfile.lockflip betweenand
with each successive
pipenv lock.3.7is also sometimes seen.Steps to replicate
Using this
Pipfile:Please run
$ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.$ pipenv --support
Pipenv version: `'2024.0.1'` Pipenv location: