@cclauss Never used pyproject.toml, so expecting lots of changes

We could also move our codespell, mypy, and pyupgrade args from .pre-commit into pyproject.toml.

Please run https://pypi.org/project/validate-pyproject to validate the file and let's add that tool to pre-commit.

We might run into trouble consolidating our pytest args because our GitHub Actions run it two different ways. So that might be difficult to express.

We could also move our codespell, mypy, and pyupgrade args from .pre-commit into pyproject.toml.

Please run https://pypi.org/project/validate-pyproject to validate the file and let's add that tool to pre-commit.

How would this be done?

The only benefit we get in using pyproject.toml is to have a central place for configuration. We don't need the project declaraction, build system, dependencies.

Build system is used to provide a backend like poetry, flit or setuptools to actually build the Python package (wheels). For our use case, requirements.txt is actually the best option instead of declaring it in pyproject.toml. Otherwise, users will be required to install using pip install . which installs the dependencies along with the package (remember this is not a package) and the egg info. Project declaration is not useful as it's used to provide metadata information for PyPi. I guess it was added to declare the dependencies which as mentioned not useful. Adding the authors field is a bit misleading as this is a work of all the contributors.

Let's use maintainers rather than authors... https://peps.python.org/pep-0621/#authors-maintainers

Would we be able to use pip install . or probably better pip install --editable . in our GitHub Actions?

Could pip install git+https://github.com/TheAlgorithms/Python.git be made to work?

As I said, this won't work as TheAlgorithms/Python is not a "Python package", you cannot install it as it's not even structured like a standard package. I don't really see why you're wasting time in this.

I fail to understand the logic. pip knows how to install project dependencies from two different file types. Why does it matter whether this is a package or not?