text: GitHub - frostming/pdm: A modern Python package manager with PEP 582 support.
  frostming / pdm Template
  A modern Python package manager with PEP 582 support. https://pdm.fming.dev/
  python packaging dependency-manager workflow pep582
  Want to be notified of new releases in frostming/pdm?
  .github bump version to 0.4.1 Mar 11, 2020
  docs Add docs for pdm import Mar 20, 2020
  news bump version to 0.6.3 Mar 30, 2020
  pdm bump version to 0.6.3 Mar 30, 2020
  tests only remove if it isn't required by any Mar 29, 2020
  .gitattributes Python version specifiers Jan 5, 2020
  .gitignore documentation Feb 26, 2020
  .pre-commit-config.yaml Fix pre-commit hook Feb 27, 2020
  CHANGELOG.md bump version to 0.6.3 Mar 30, 2020
  CODE_OF_CONDUCT.md switch to pypa CoC Feb 12, 2020
  CONTRIBUTING.md update CONTRIBUTING.md Feb 19, 2020
  LICENSE synchronize dependencies function Jan 18, 2020
  README.md Update README Mar 14, 2020
  README_zh.md Update README Mar 14, 2020
  pdm.lock fix lockfile Mar 29, 2020
  setup.cfg update pdm dependencies Mar 28, 2020
  setup_dev.py sequential install Mar 29, 2020
  PDM is meant to be a next generation Python package management tool. It is originally built for personal interest. If you feel you are going well with Pipenv or Poetry and don't want to introduce another package manager, just stick to it. But if you are missing something that is not present in those tools, you can probably find some goodness in pdm.
  Now the majority of Python packaging tools also act as virtualenv managers. It is for the benifit of isolating project environments. But things will get tricky when it comes to nested venvs: One installs the virtualenv manager using a venv capsulated Python, and create more venvs using the tool which is based on a capsulated Python. One day a minor release of Python out and one has to check all those venvs and upgrade them if required.
  While PEP 582, in the other hand, introduce a way to decouple Python interpreter with project environments. It is a relative new proposal and there are not many tools supporting it, among which there is pyflow, but it is written with Rust and can't get much help from the big Python community. Moreover, due to the same reason, it can't act as a PEP 517 backend.
  It is recommended to install pdm in an isolated enviroment, with pipx.
  Or you can install it under user site:
  python -m pdm --help should be a good guidance.
  PEP 582 is a draft proposal which still needs a lot of polishment, for instance, it doesn't mention how to manage CLI executables. PDM take the decision to put bin, include together with lib under __pypackages__/X.Y.
  The recommended way is to prefix your command with pdm run. It is also possible to run CLI scripts directly from the outside, the PDM's installer has already injected the package path to the sys.path in the entry script file.
  PDM first looks to __pypackages__ but will fall back to looking in site-packages. This is not entirely hermetic and could lead to some confusion around which packages are being used, though.