-
As prototyped in #646, I believe this repo is a nice place to house a general parsing and validation function for the PEP 621 `[project]` table in the `pyproject.toml`.
This returns a list of (buil…
-
## 🚀 Feature
`pyproject.toml` is the new standard for packaging python packages, `setup.py` is now deprecated (first introduced in [PEP 518](https://peps.python.org/pep-0518/) and later expanded in…
-
### Summary
Hello,
As a newcomer to the python packaging world I was redirected from python.org to the setuptools documentation because python recommended it as the first choice for packaging. I h…
-
- [x] I have searched the [issues](https://github.com/python-poetry/poetry/issues) of this repo and believe that this is not a duplicate.
- [x] I have searched the [documentation](https://python-poet…
-
The Python packaging ecosystem has been working hard to bring more standardization, such that you don't "have" to use pip and setuptools.
PEPs 517 and 621 are particularly relevant for metadata fo…
-
-
Starting with [PEP 621](https://peps.python.org/pep-0621/), the Python community selected `pyproject.toml` as the standard way to specify project metadata. This is beneficial as all packaging tools wi…
-
[PEP 631](https://www.python.org/dev/peps/pep-0631/)
I may be misunderstanding, but looking at the PEP, I think it means that dependency specification within a `pyproject.toml` is getting standardi…
-
🐞 **Problem**
Similar situation as in #46. Duplicated instances of `pyproject.toml` for the build-system tools flit and poetry.
💡 **Solution**
Combine those into a single file.
-
**Describe the bug**
[PEP 621](https://www.python.org/dev/peps/pep-0621/) allows project metadata to be defined in `pyproject.toml`. This uses a list of dictionaries to represent the project's author…