On Thu, 10 Jul 2025, Miro Hrončok wrote:
On 10. 07. 25 2:45, Scott Talbert wrote:
The one thing - %pyproject_save_files can't work in the case of building
multiple wheels in the same package, right?
Correct. As ow now, it has no API to say "save files from package X", so when
multiple whee
On 10. 07. 25 2:45, Scott Talbert wrote:
The one thing - %pyproject_save_files can't work in the case of building
multiple wheels in the same package, right?
Correct. As ow now, it has no API to say "save files from package X", so when
multiple wheels are installed in %pyproject_install, we
On Wed, 9 Jul 2025, Miro Hrončok via python-devel wrote:
On 09. 07. 25 4:31, Scott Talbert via python-devel wrote:
Is there any way to use the pyproject macros when setup.py isn't in the
root directory?
I maintain a couple of packages where this is the case - one where there
are actually two
On 09. 07. 25 4:31, Scott Talbert via python-devel wrote:
Is there any way to use the pyproject macros when setup.py isn't in the root
directory?
I maintain a couple of packages where this is the case - one where there are
actually two PyPI packages built from the same source package, and anot
Hi Scott
Scott Talbert via python-devel venit, vidit, dixit 2025-07-09 04:31:15:
> Is there any way to use the pyproject macros when setup.py isn't in the
> root directory?
>
> I maintain a couple of packages where this is the case - one where there
> are actually two PyPI packages built from t
Is there any way to use the pyproject macros when setup.py isn't in the
root directory?
I maintain a couple of packages where this is the case - one where there
are actually two PyPI packages built from the same source package, and
another where the Python package is in a subdirectory because
