delta/python-setuptools-git.git/docs/build_meta.rst, branch dev/core_metadata

Use separated import statement to avoid copying names

2023-04-20T12:45:39+00:00

🎨📝 Fix in-tree PEP 517 backend wrapper example

2023-04-16T00:26:00+00:00

Before this patch, the documentation suggested the package authors to
declare a fixed set of hooks inherited from setuptools. But this
approach turned out non-future proof. Over time, as `setuptools` added
support for editable installs, it introduced new hooks per PEP 660.
But if one were to follow the outlined example, they'd end up with an
in-tree build backend that does not support editable installs, nor
would it re-export any hooks that might be added in future versions of
setuptools, implementing any new standards that may emerge over time.

This change demonstrates an approach that would allow the thin wrapper
authors to get the new hooks that setuptools may add over time.

Ref: https://github.com/ansible/ansible/pull/79606#discussion_r1080753862

Use Sphinx :pep: role to link directly to PEPs

2023-01-14T15:05:03+00:00

fix documentation for dynamic build dependencies

2022-12-20T03:47:31+00:00

Get rid of trailing spaces, mainly in docs

2022-11-20T20:05:08+00:00

Remove wheel dependency in example

2022-07-08T13:00:13+00:00

Add beta status to 'file' directive for reading dependencies

2022-06-19T18:31:21+00:00

Update build_meta.rst

2022-06-18T00:55:48+00:00

Update docs/build_meta.rst

2022-06-18T00:15:02+00:00

Co-authored-by: Anderson Bravalheri

Update build_meta.rst

2022-06-17T06:32:44+00:00

Mainly grammar/style tweaks... which turned into a few more thoughts:
About this statement: "decide which program to use to 'build from source' (the default is ``setuptools``)." 
I think 'default' conveys the wrong impression here when it is explaining the new way of doing things. PEP517 says, "(build) tools should revert to the legacy behaviour of running setup.py" Maybe a footnote would be better saying it is a fallback, for backward compatibility. (But, all the same, this is interesting information that now explains to me why 'py -m build' worked before I had tried using a pyproject.toml file.)
Line 37:  ``build_meta`` implements ``setuptools``'s build system support.
This seems out of place, and doesn't make sense. build_meta hasn't been mentioned yet in this article. Maybe this sentence could go before line 61.
Line 26-28: This seems like low-level detail that is out of place in this article. If you want to keep it, maybe add a note that the default directory is dist\.
**The "bullet items" under the PEP517 section aren't formatting correctly in the Preview. Please check that I haven't messed anything up there in the final render.