For what it's worth, pyproject.toml seems to have been adopted without much friction in SciPy. In some CI runs in SciPy, we use something like "pip wheel --no-build-isolation -v -v -v" to disable the isolation in any case.
I suppose NumPy is indeed even closer to the base of the ecosystem, but the ease of disabling may mitigate concerns related to switching from system-installed dependencies to an isolated environment for a naive "pip install" Tyler On Sun, 14 Jul 2019 at 08:47, Matti Picus <matti.pi...@gmail.com> wrote: > In PR #13908 I implemented the previously-discussed new method of creating > the release notes: writing separate fragments and then combining them at > release time via towncrier. Towncrier requires a PEP-508/PEP-517/PEP-518 > pyproject.toml file for configuration, and does not currently support a > command line option to specify a different location for this file. That > means that we now must ship a pyproject.toml file, which subtlely changes > the way "pip install ." builds NumPy: it does an "isolated build" > https://pip.pypa.io/en/stable/reference/pip/#pep-517-and-518-support > > > Questions: > > - Is the pain of adding a pyproject.toml worth it for using towncrier or > should we o for another release-note solution > > - Is the addition of pyproject.toml problematic enough that I should break > it out into a separate pull request for evaluation? > > > Matti > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
