-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipenv requirements
does not include markers
#5092
Labels
Type: Bug 🐛
This issue is a bug.
Comments
matteius
changed the title
May 2, 2022
pipenv requiremetns
does not include markerspipenv requirements
does not include markers
We are also having this issue, and have reverted back to the lock mechanism. |
It looks like micropipenv requirements provides expected output. |
@matteius shall I create a PR for this over the weekend? |
@ImreC That would be awesome 😎 |
Ok, forgot to do this. Will pick it up end of this week. |
PR open #5114 |
oz123
pushed a commit
that referenced
this issue
Jun 25, 2022
cakekoa
added a commit
to guardicore/monkey
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
cakekoa
added a commit
to guardicore/monkey
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
cakekoa
added a commit
to guardicore/monkey
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Feb 28, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
to guardicore/monkey
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just tried to use
pipenv reqirements
instead ofpipenv lock --requirements
but it lacks markers so windows only dependencies from my lock file makespip install -r ...
fail.example transitive dependency form lock file that at some point was locked on a windows machine:
Running
pipenv lock --requirements --keep-outdated
(on linux) results in:Running
pipenv requirements
(on linux) has no marker so the requirements file fails to install on linux.pipenv, version 2022.4.30
The text was updated successfully, but these errors were encountered: