Hi Miro,
On Wed, Feb 5, 2025, at 3:47 AM, Miro Hrončok via python-devel wrote:
> Hello Pythonistas.
>
> When we updated tox from version 3 to 4, it no longer fails when here is no
> suitable tox configuration found. This was a deliberate upstream choice.
>
> Unfortunately, it means that packages
On 2/5/25 02:47, Miro Hrončok via python-devel wrote:
Hello Pythonistas.
When we updated tox from version 3 to 4, it no longer fails when here is
no suitable tox configuration found. This was a deliberate upstream choice.
Unfortunately, it means that packages that use %pyproject_buildrequires
On 05. 02. 25 10:47, Miro Hrončok wrote:
Hello Pythonistas.
When we updated tox from version 3 to 4, it no longer fails when here is no
suitable tox configuration found. This was a deliberate upstream choice.
Unfortunately, it means that packages that use %pyproject_buildrequires with -t
or
Hello Pythonistas.
When we updated tox from version 3 to 4, it no longer fails when here is no
suitable tox configuration found. This was a deliberate upstream choice.
Unfortunately, it means that packages that use %pyproject_buildrequires with -t
or -e now silently succeed if there is no tox
