Skip to content

P
python-poetry
Switch branch/tag
  1. 17 Sep, 2022 2 commits
  3. 16 Sep, 2022 2 commits
  5. 15 Sep, 2022 2 commits
  7. 14 Sep, 2022 2 commits
  9. 13 Sep, 2022 1 commit
  11. 12 Sep, 2022 2 commits
  13. 11 Sep, 2022 3 commits
  15. 10 Sep, 2022 1 commit
  17. 09 Sep, 2022 3 commits
  19. 08 Sep, 2022 2 commits
  21. 07 Sep, 2022 1 commit
  23. 06 Sep, 2022 5 commits
    • Fix shell activation for zsh (#5795) · 28d0175d 
      # Fix Shell Activation For ZSH

This PR resolves an issue wherein poetry will clear the `PATH` on zsh.
The activation script contains a number of if statements of the
following form:

```bash
    # ...
    if ! [ -z "${_OLD_VIRTUAL_PATH:+_}" ] ; then
        PATH="$_OLD_VIRTUAL_PATH"
        export PATH
        unset _OLD_VIRTUAL_PATH
    fi
```
These constructs are valid in bash, although zsh fails to negate the
conditional except when placed in emulation mode:

```zsh
# Causes PATH to be cleared, leading to other issues
. /home/alecto/.cache/pypoetry/virtualenvs/poetry-E-aAiPjf-py3.10/bin/activate
```

When bash is used as an emulator to source the script, it functions
correctly:

```zsh
# Functions correctly
emulate bash -c '. /home/alecto/.cache/pypoetry/virtualenvs/poetry-E-aAiPjf-py3.10/bin/activate'
```

It's important to note that this doesn't place the *entire* shell into
bash emulation mode; only the activate script is sourced as bash.

Any guidance on what tests should be added for this PR would be
appreciated.

Co-authored-by: Alecto Irene Perez <alecto.perez@voladynamics.com>
Co-authored-by: Bartosz Sokorski <b.sokorski@gmail.com>
      Alecto Irene Perez committed
    • fix: write to stderr in utils.env · 47255c44 
      This is a quick fix to avoid polluting stdout unexpectedly when Poetry's
environment management comes into play.

It's apparent from how much the complexity of this file has grown that
this needs to be refactored moderately, as well as each major class
deserving its own source file.

Future work should also include a rethink of how IO objects are passed
around the codebase, how we reason about verbosity at a function level,
and how code is re-used -- one command may wish to output to stdout, but
if that code is reused by another command, the calculus of what is
command output and what is informative (or even needs to be hidden/shown
based on verbosity level) changes.

Work on output would likely have to be fairly comprehensive and
invasive, but things have grown complex enough that a top-down design
pass is likely the best route.

Regardless, this is a simple change today, and low risk. Resolves #6427.
      Bjorn Neergaard committed
    • env: prefer "python -m pip" to calling pip directly to allow pip updating itself on Windows · b9ed1f05
      Randy Döring committed
    • refactor(env): remove duplicated implementations of get_pip_command() · 3bdc3972
      Randy Döring committed
    • [pre-commit.ci] pre-commit autoupdate (#6414) · 40780824 
      <!--pre-commit.ci start-->
updates:
- [github.com/psf/black: 22.6.0 → 22.8.0](https://github.com/psf/black/compare/22.6.0...22.8.0)
<!--pre-commit.ci end-->

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
      pre-commit-ci[bot] committed
  25. 05 Sep, 2022 3 commits
  27. 04 Sep, 2022 2 commits
  29. 03 Sep, 2022 5 commits
  31. 02 Sep, 2022 4 commits