4 Commits (cdd36b908d2c34bd72f9c6f13656df2ecc59c8f9)

Author	SHA1	Message	Date
Matt Clay	dbd928cad9	[stable-2.14] release.py - Auto-update setuptools upper bound (#83713) (#83745) ... * [stable-2.14] release.py - Auto-update setuptools upper bound (#83713) When releases are prepared, the upper bound on setuptools in pyproject.toml will be automatically updated to the latest version available on PyPI. This version will then be tested by the package-data sanity test during the release process and will be used to build the release. This change ensures that a released version of ansible-core can be built in the future if a new setuptools release includes breaking changes that would prevent building a functional package. If a downstream package maintainer requires a newer setuptools version than the upper bound permits, they can patch pyproject.toml as needed. Since ansible-core releases support specific Python versions, lack of support for new setuptools releases will have no effect on support for future Python versions. (cherry picked from commit 4e69d83fac) * release.py - Add missing setuptools arg to prepare (#83887) * release.py - Add missing setuptools arg to prepare This allows the prepare command to accept the `--no-setuptools` argument. It also fixes a traceback when using the `prepare` command. * Use a more accurate type hint (cherry picked from commit b544ac13ec) * release.py - Include pyproject.toml in git add (#83892) (cherry picked from commit e3ccdaaa2e)	2 months ago
Matt Clay	dd45caa7a9	[stable-2.14] Docs removal and other backports (#81407) ... * Remove straight.plugin dependency (#80084) (cherry picked from commit f587856beb) * Update package-data sanity test (#80344) The test no longer relies on the Makefile. (cherry picked from commit 46362bbd27) * Remove obsolete release bits (#80347) Releases are now built using the `packaging/release.py` tool. This makes the `Makefile` and associated files in `packaging/release/` and `packaging/sdist/` obsolete. * Use --no-isolation for package-data sanity test (#80377) The dependencies are already in the sanity test venv. This avoids use of unpinned dependencies and a dependency on a network connection. (cherry picked from commit 7fcb9960e6) * Set the minimum setuptools to 45.2.0 (#80649) Also update the package-data sanity test to use the minimum setuptools version. (cherry picked from commit 4d25e3d54f) * Use package_data instead of include_package_data (#80652) This resolves warnings generated by setuptools such as the following: _Warning: Package 'ansible.galaxy.data' is absent from the `packages` configuration. (cherry picked from commit 5ac292e12d) * Fix os.walk issues in package-data sanity test (#80703) * Remove `docs` and `examples` directories (#81011) * Remove docs dir * Updates to reflect docs removal * Fix integration test * Remove examples dir * Updates to reflect examples removal * Remove build_library and build-ansible.py * Remove refs to build_library and build-ansible.py * Remove obsolete template * Remove obsolete template reference * Remove the now obsolete rstcheck sanity test (cherry picked from commit 72e038e823) * Omit pre-built man pages from sdist (#81395) Since man pages aren't accessible to users after a `pip install`, there's no need to include them in the sdist. This change makes it trivial to build man pages from source, which makes them much easier to iterate on. It also simplifies creation and testing of the sdist, since it no longer requires building man pages. The new `packaging/cli-doc/build.py` script can generate both man pages and RST documentation. This supports inclusion on the docs site without a dependency on `ansible-core` internals. Having a single implementation for both simplifies keeping the two formats in sync. (cherry picked from commit 691c8e8603)	1 year ago
Sviatoslav Sydorenko	bfc26f55cc	[backport-2.14] 📦 Integrate manpage builds into PEP 517 build backend (#80129) ... This patch creates a thin wrapper around the `setuptools`' PEP 517 build backend in-tree. It features an ability to request generating the manpage files in the process of building a source distribution. This toggle is implemented using the `config_settings` mechanism of PEP 517. One must explicitly pass it a CLI option to the build front-end to trigger said behavior. The packagers are expected to use the following call: python -m build --config-setting=--build-manpages This option has no effect on building wheels. 🧪 The change includes integration tests This test runs building and re-building sdists and wheels with and without the `--build-manpages` config setting under the oldest-supported and new `setuptools` pinned. It is intended to preserve the interoperability of the packaging setup across Python runtimes. An extra smoke test also verifies that non PEP 517 interfaces remain functional. PR #79606 Co-authored-by: Matt Clay <matt@mystile.com> (cherry picked from commit 56036013cd)	2 years ago
Matt Martz	66a83314b9	Modernize install (#76021) ... Co-authored-by: Matt Clay <matt@mystile.com> Co-authored-by: Matt Davis <mrd@redhat.com> Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>	3 years ago