|
| 1 | +2026.6.0 (2026-04-27) |
| 2 | +===================== |
| 3 | +pipenv 2026.6.0 (2026-04-27) |
| 4 | +============================ |
| 5 | + |
| 6 | + |
| 7 | +Bug Fixes |
| 8 | +--------- |
| 9 | + |
| 10 | +- Fix ``pipenv shell`` breaking terminal input echo on Linux. The previous |
| 11 | + implementation toggled ``setecho(True/False)`` on the spawned child around |
| 12 | + its internal setup commands, which fought with the shell's own readline |
| 13 | + termios management — producing permanently-disabled echo (GH-6572) or |
| 14 | + double-echoed keystrokes (``1234`` → ``11223344``). ``fork_compat`` no |
| 15 | + longer touches pty termios; instead it drains the synchronisation sentinel |
| 16 | + from the pexpect buffer twice (once for the echoed command, once for its |
| 17 | + output) so nothing leaks into ``interact()``. `#6633 <https://github.com/pypa/pipenv/issues/6633>`_ |
| 18 | +- ``pipenv run <command> -h <arg>`` now passes ``-h`` through to the command |
| 19 | + instead of showing pipenv's help. All arguments following ``run_command`` are |
| 20 | + captured verbatim via argparse ``REMAINDER``, so flags like ``-h`` that pipenv |
| 21 | + itself also defines no longer collide with the wrapped command. `#6641 <https://github.com/pypa/pipenv/issues/6641>`_ |
| 22 | +- Fix ``ValueError: invalid literal for int() with base 10`` when the Pipfile's |
| 23 | + ``[requires]`` section uses a PEP 440 specifier (e.g. ``python_version = ">=3.9"``). |
| 24 | + Specifier values no longer produce a Python-version override; the running |
| 25 | + interpreter's actual version is used for marker evaluation instead. `#6645 <https://github.com/pypa/pipenv/issues/6645>`_ |
| 26 | +- Install-time marker filtering now evaluates environment markers against the |
| 27 | + target virtualenv's Python version rather than against the Python version |
| 28 | + that pipenv itself is running under. This prevents spurious ``Ignoring …: |
| 29 | + markers … don't match your environment`` warnings (and the corresponding |
| 30 | + missing installs) when ``pipenv sync --python X.Y`` is driven by a |
| 31 | + different system Python. `#6647 <https://github.com/pypa/pipenv/issues/6647>`_ |
| 32 | +- ``pipenv run`` now expands ``$PIPENV_PROJECT_DIR`` and other Pipenv-managed |
| 33 | + environment variables inside Pipfile script arguments before direct command |
| 34 | + execution, so project-relative script paths resolve correctly. `#6652 <https://github.com/pypa/pipenv/issues/6652>`_ |
| 35 | + |
| 36 | +Improved Documentation |
| 37 | +---------------------- |
| 38 | + |
| 39 | +- Pipfile documentation now includes git+ssh examples. `#6651 <https://github.com/pypa/pipenv/issues/6651>`_ |
| 40 | + |
1 | 41 | 2026.5.2 (2026-04-03) |
2 | 42 | ===================== |
3 | 43 | pipenv 2026.5.2 (2026-04-03) |
|
0 commit comments