migrate packaging to pyproject.toml

[deronnax]

Just an initiative of my own.

[deronnax]

OK, it's almost ready except:

• It can't work on python 3.6 because having setuptools being able to read metadata from pyproject.toml requires setuptools > 61.2, which does not support python 3.6 anymore.
• I need to figure out what is conftest.py doing with the package_root

[terencehonles]

• I need to figure out what is conftest.py doing with the package_root

This is unrelated to your PR and I fixed it with #9129

[deronnax]

Wow. It works indeed. Thank you so much.

[auvipy]

We need to hold this off for now. As we got other priorities.

[deronnax]

Sure. A vague estimation of when it would become envisageable ?

[deronnax]

To merge after #9210, I hope.

[deronnax]

watch-out: this PR is intended to be squash-merged

[tomchristie]

So... this is a good example of a nice little pr that's a bit stalled. I don't really have any extra bandwidth to keep this moving, given existing commitments. Should we be having a discussion about getting the project into jazzband.co so that we've got a lower barrier of entry for new maintainers?

[deronnax]

Hey, that's a very interesting decision that is (way) beyond the scope of my humble little PR. Maybe let's open a dedicated issue ou GitHub discussion?

[ulgens]

Is this still true?

[deronnax]

not in the current state, indeed

[deronnax]

So, for remember, python 3.6 support is removed in this PR because of setuptools > 61.2 which is required for pyproject.toml support, does not support python 3.6.
I also did #9133, in which python support is discussed, and we figured that according to our policy, we still need to support python 3.6 and 3.7 because the last django we currently support, the 3.2, still supports them. So this MR can't be merged until we drop support of django 3.2 (which would be when django 5.2 is released, mid-2024).

Technically I could do a version of this PR were DRF could not be built on python 3.6 anymore, but still be installed on it, but that would be I think a lot of CI work, and it's simpler to just wait 3 months.

To hold until Django 5.2 is released, then.

[auvipy]

So... this is a good example of a nice little pr that's a bit stalled. I don't really have any extra bandwidth to keep this moving, given existing commitments. Should we be having a discussion about getting the project into jazzband.co so that we've got a lower barrier of entry for new maintainers?

No.

[deronnax]

@auvipy what do you propose then? DRF has been zombie for at least 2 years. PRs are not reviewed, questions are not answered.