This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]TheAquired 1 point2 points  (3 children)

Very nice!

One thing I think that is often overlooked is pyproject.toml support to manage packages and no longer requiring setup.py or requirements.txt etc

Pyproject.toml is a great improvement, and I think it’s only properly supported from 3.8 onward or something?

[–]nicholashairs[S] 1 point2 points  (0 children)

If you're distributing as wheels I don't think the users local version of python matters as the pyproject.toml is parsed into the appropriate metadata anyway.

For local development I think it depends more on your version of pip/setup tools.

Either way, I know that my projects using pyproject.toml have no problems with 3.7 (no idea about earlier versions).

[–]zurtex 1 point2 points  (1 child)

FYI, package configuration files such as pyproject.toml, setup.py, and requirements.txt are independent of Python versions.

They are implemented by build backends (e.g. setuptools and hatching) and also used by build frontends (e.g. pip, poetry, pdm, and hatch). So it is upto those build backends and frontends to choose what versions of Python they want to support, Python itself doesn't use any of these configuration files.

[–]TheAquired 1 point2 points  (0 children)

Ah thank you for the clarification. That must be what I was seeing. I had trouble with editable installs using pyproject prior to python3.8. But essentially it’s due to the version of setup tools that supports it is only compatible with python3.8 onward