A modern Python package manager with PEP 582 support. 中文版本说明
PDM is meant to be a next generation Python package management tool.
It was originally built for personal use. If you feel you are going well
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
PEP 582 proposes a project structure as below:
foo __pypackages__ 3.8 lib bottle myscript.py
There is a
__pypackages__ directory in the project root to hold all dependent libraries, just like what
Read more about the specification here.
The majority of Python packaging tools also act as virtualenv managers to gain the ability to isolate project environments. But things get tricky when it comes to nested venvs: One installs the virtualenv manager using a venv encapsulated Python, and create more venvs using the tool which is based on an encapsulated Python. One day a minor release of Python is released and one has to check all those venvs and upgrade them if required.
PEP 582, on the other hand, introduces a way to decouple the Python interpreter from project environments. It is a relative new proposal and there are not many tools supporting it (one that does is pyflow), but it is written with Rust and thus can't get much help from the big Python community. For the same reason it can't act as a PEP 517 backend.
PDM requires python version 3.7 or higher.
If you are on MacOS and using
homebrew, install it by:
$ brew install pdm
Otherwise, it is recommended to install
pdm in an isolated environment with
$ pipx install pdm
Or you can install it under a user site:
$ pip install --user pdm
Initialize a new PDM project
$ pdm init
Answer the questions following the guide, and a PDM project with a
pyproject.toml file will be ready to use.
Install dependencies into the
$ pdm add requests flask
You can add multiple dependencies in the same command. After a while, check the
pdm.lock file to see what is locked for each package.
Run your script with PEP 582 support
Suppose you have a script
app.py placed next to the
__pypackages__ directory with the following content(taken from Flask's website):
from flask import Flask app = Flask(__name__) @app.route('/') def hello_world(): return 'Hello World!' if __name__ == '__main__': app.run()
If you are a Bash user, set the environment variable by
eval $(pdm --pep582). Now you can run the app directly with your familiar Python interpreter:
$ python /home/frostming/workspace/flask_app/app.py * Serving Flask app "app" (lazy loading) ... * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
Ta-da! You are running an app with its dependencies installed in an isolated place, while no virtualenv is involved.
For Windows users, please refer to the doc about how to make it work.
If you are curious about how this works, check this doc section for some explanation.
$ docker pull frostming/pdm
PEP 582 is a draft proposal which still needs a lot of polishing. For instance, it doesn't mention how to manage
CLI executables. PDM makes the decision to put
include together with
The recommended way is to prefix your command with
pdm run. It is also possible to run CLI scripts directly from
the outside. PDM's installer has already injected the package path to the
sys.path in the entry script file.
Packages in the local
__pypackages__ directory will be loaded before the system-level
site-packages for isolation.
__pypackages__folder for deployment?
You'd better not. The packages installed inside
__pypackages__ are OS dependent. Instead, you should keep
in VCS and do
pdm sync on the target environment to deploy.
pdmto manage a Python 2.7 project?
pdm itself can be installed under Python 3.7+ only, but it doesn't restrict the Python used by the project.
Tell people you are using PDM in your project by including the markdown code in README.md:
This project is open sourced under MIT license, see the LICENSE file for more details.