Update generated validation code using validate_pyproject==0.12.1

[abravalheri]

Summary of changes

• Bump validate_pyproject==0.12.1 in tox.ini
• Update generated validation code

Closes #3796

Pull Request Checklist

• Changes have tests
  • Tested in https://github.com/abravalheri/validate-pyproject/blob/main/tests/examples/setuptools/08-pyproject.toml
  • Tested in https://github.com/abravalheri/validate-pyproject/blob/main/tests/examples/setuptools/09-pyproject.toml
• News fragment added in changelog.d/.
  (See documentation for details)

[b-kamphorst]

Hi @abravalheri! This PR allows stub names in packages. Just checking: does it also allow stub names in the keys of package-dir (and possibly other attributes where this is sensible)?

[abravalheri]

Do you want to map your package directory to a different folder?

That would require further changes.

Do you know if basic setup.py handles package_dir with stub names?

[b-kamphorst]

Do you want to map your package directory to a different folder?

That would require further changes.

Do you know if basic setup.py handles package_dir with stub names?

Yes, we currently have a setup.cfg that has this section:

name = namespace.mod.stubs

[options]
packages =
    otherpkg-stubs
    namespace.mod.stubs
package_dir =
    otherpkg-stubs = namespace/mod/stubs

I'm not saying this is the best approach. If we install our package, it will install the package content twice -- once as the stubs of another package, and once as a standalone package in our namespace. Our package is not stub-only -- it provides stubs of another package but also two function wrappers that are needed to perform better type annotation with the other package. These wrappers should be imported by clients and therefore we provide a non-stubs import that allows that.

[abravalheri]

I'm not saying this is the best approach.

No problems. Thank you very much for the example, it should be enough to create a test for it.

Sorry, I did not understand that part at first!

[b-kamphorst]

Sorry, I did not understand that part at first!

No problem at all!

Again I am pleasantly surprised by your quick response. Moreover, I can confirm that this PR solves my issue. Looking forward to the release and thank you so much!

[abravalheri]

Probably next week. I try to avoid releases on Friday 😝

[b-kamphorst]

Probably next week. I try to avoid releases on Friday 😝

That is quite sensible 😅