ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Since mid 2022 it is now possible to get rid of setup.py , setup.cfg in favor of pyproject.toml . Editable installs work with recent versions of setuptools and pip and even the official packaging tutorial switched away from setup.py to pyproject.toml . However, documentation regarding requirements.txt seems to be have been also removed, and I wonder where to
I'm trying to migrate a setuptools -based project from the legacy setup.py towards modern pyproject.toml configuration. At the same time I want to keep well established workflows based on pip-compile , i.e., a requirements.in that gets compiled to a requirements.txt (for end-user / non-library projects of course). This has important benefits as a result of t
When a project is specified only via pyproject.toml (i.e. no setup.{py,cfg} files), how can it be installed in editable mode via pip (i.e. python -m pip install -e . )? I tried both setuptools and poetry for the build system, but neither worked: [build-system] requires = ["setuptools", "wheel"] build-backend = "setuptools.build_meta" [build-system] requires
Background I was about to try Python package downloaded from GitHub, and realized that it did not have a setup.py , so I could not install it with pip install -e <folder> Instead, the package had a pyproject.toml file which seems to have very similar entries as the setup.py usually has. What I found Googling lead me into PEP-518 and it gives some criti
python