the brew still could not install 2.10.1

[jiangxiaoqiang]

$ brew install pdm                                                                                                                                   ‹ruby-2.7.2›
==> Downloading https://ghcr.io/v2/homebrew/core/pdm/manifests/2.9.3
Already downloaded: /Users/dolphin/Library/Caches/Homebrew/downloads/b9b331e42261fca1679ab6232b33ae7dfa065daf50efcd7281b795875dec9031--pdm-2.9.3.bottle_manifest.json
==> Fetching pdm
==> Downloading https://ghcr.io/v2/homebrew/core/pdm/blobs/sha256:d7e320e2753a87ccb2a0253760926e2a9ba596d1d3dffd15be710345b0c5338b
Already downloaded: /Users/dolphin/Library/Caches/Homebrew/downloads/c143f1260bf311eb99511f1be49821d5916149199e54b633c5ea5a54b901e031--pdm--2.9.3.ventura.bottle.tar.gz
==> Pouring pdm--2.9.3.ventura.bottle.tar.gz
==> Caveats
zsh completions have been installed to:
  /usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/pdm/2.9.3: 949 files, 11.5MB
==> Running `brew cleanup pdm`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
(venv) (base) 

[pawamoy]

I suppose something needs to be updated on brew's side?

[frostming]

run brew update and try again. it's not pdm's fault

[baggiponte]

I would also like to add I believe that installing pdm with brew could raise some issues. I don't know if brew creates separate virtual environments for every python dependency it adds, but it might be safer to brew install pipx and use pipx to install pdm and other python CLIs. pipx ensures they will be installed in a virtual environment just for them. Maybe brew does the same, though?

[frostming]

yes, brew also installs pdm in a virtualenv, just it packs and builds all dependencies itself, and some of the dependencies are brew formulae themselves and they must be included by depends_on key.

https://github.com/Homebrew/homebrew-core/blob/master/Formula/p/pdm.rb

[frostming]

The error happens when the PDM formula is migrated to [email protected] but not all of its dependencies upgrade at the same time. So there may be still dependencies on [email protected]. In this case they will pass the dependency check but can't be found in an [email protected] environment.

[baggiponte]

thanks for the explanation!