3 ms·
We are. pyproject.toml is now our official record of dependencies, command-line scripts, etc. for all recently-touched repos. We've updated most built tooling t
by kstrauser 7y ago
We are. pyproject.toml is now our official record of dependencies, command-line scripts, etc. for all recently-touched repos. We've updated most built tooling to use `poetry install` instead of `pip install -r requirements.txt`. In places where we haven't yet, we have Makefile targets like:
# Generate setup.py and requirements.py until we can get off that treadmill.
# This *must* be done every time you update dependencies, as pyproject.toml is
# now the official source of project configuration and packages.
python_oldfiles:
dephell deps convert; dephell deps convert --env requirements
and pyproject.toml blocks:
[tool.dephell.main]
from = {format = "poetry", path = "pyproject.toml"}
to = {format = "setuppy", path = "setup.py"}
[tool.dephell.requirements]
from = {format = "poetry", path = "pyproject.toml"}
to = {format = "pip", path = "requirements.txt"}
Now when a dev does `poetry add foo`, they can run `make python_oldfiles` to autogenerate updated "compatibility" files.