Modernize python package setup#331
Conversation
Alicipy
force-pushed
the
modernize-python-package-setup
branch
from
3a02cec to
549244d
Compare
|
Yes of course, I would love to! How do you suggest to proceed? Shall we merge this and redo the other one, or vice versa? This change does work in both, poetry and uv; as it depends only on PEP-specified behaviour right now. |
Alicipy
force-pushed
the
modernize-python-package-setup
branch
from
549244d to
973251f
Compare
Lets any packaging tool read the metadata, not just Poetry, and puts the fields as described in https://packaging.python.org/en/latest/specifications/pyproject-toml/#pyproject-toml-spec Signed-off-by: Stefan Kraus <dev@stefankraus.org>
[dependency-groups] is the standard table for these now Signed-off-by: Stefan Kraus <dev@stefankraus.org>
hatchling is the PyPA-maintained build backend; building a wheel no longer needs Poetry installed. Poetry can stay for the workflow. Signed-off-by: Stefan Kraus <dev@stefankraus.org>
This is done automatically as it's part of pytm package Signed-off-by: Stefan Kraus <dev@stefankraus.org>
Probably missed from a previous migration, most used repo lives at OWASP/pytm now. Signed-off-by: Stefan Kraus <dev@stefankraus.org>
Alicipy
force-pushed
the
modernize-python-package-setup
branch
from
973251f to
fccb68b
Compare
|
@Alicipy You missed the github ci related changes I guess. Some other notes: gitbook support seems to be deprecated. Using a docs dir is the defacto standard compatible with mkdocs and other Python ecosystem static documentation generators. I‘d recommmend to have a look into https://github.com/OWASP/pytm/pull/305/changes#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711 (and the overall PR) which addresses those topics already. |
3 participants
While starting with pytm, I saw a few things regarding package management that could use improvement, especially as the Python folks use pure pip or uv currently, and maybe wondering why the commands don't work.
This PR includes migration to the default pyproject.toml keys which poetry in version 2 also understands, so nothing breaks. As pip can handle these as well, we can remove a few other files which existed for compatibility reasons (?) as well.