On Wed, Apr 10, 2024 at 2:23 PM Miro Hrončok wrote:
>
> Hello Pythonistas,
>
> Python 3.13 has an experimental JIT compiler:
>
> https://docs.python.org/dev/whatsnew/3.13.html#experimental-jit-compiler
>
> Enabling it is a configure (hence build-time) option.
>
> How do we handle this in Fedora?
On Wed, Apr 10, 2024 at 8:23 PM Miro Hrončok wrote:
> Hello Pythonistas,
>
> Python 3.13 has an experimental JIT compiler:
>
> https://docs.python.org/dev/whatsnew/3.13.html#experimental-jit-compiler
>
> Enabling it is a configure (hence build-time) option.
>
> How do we handle this in Fedora?
>
Hello Pythonistas,
Python 3.13 has an experimental JIT compiler:
https://docs.python.org/dev/whatsnew/3.13.html#experimental-jit-compiler
Enabling it is a configure (hence build-time) option.
How do we handle this in Fedora?
- We can keep it disabled, as it is experimental.
- We can enable
On 10. 04. 24 17:30, Sandro wrote:
On 10-04-2024 12:04, Miro Hrončok wrote:
On 09. 04. 24 19:30, Sandro wrote:
Therefore, I'm thinking of introducing pynose as a drop in replacement of
deprecated nose. Pynose uses the same namespace as nose, but provides
python3dist(pynose). Thus adding
On 10-04-2024 12:04, Miro Hrončok wrote:
On 09. 04. 24 19:30, Sandro wrote:
Therefore, I'm thinking of introducing pynose as a drop in replacement
of deprecated nose. Pynose uses the same namespace as nose, but
provides python3dist(pynose). Thus adding Provides: for nose would
make it a
On 10-04-2024 11:57, Lumír Balhar wrote:
This sounds like an interesting idea for one more reason. We are
currently working on the update of pytest to version 8 and that version
no longer runs nose setup/teardown functions/methods which, as far as we
know now, is a change that breaks a lot of
On 09. 04. 24 19:30, Sandro wrote:
Therefore, I'm thinking of introducing pynose as a drop in replacement of
deprecated nose. Pynose uses the same namespace as nose, but provides
python3dist(pynose). Thus adding Provides: for nose would make it a drop-in
replacement for packages currently
Hi.
This sounds like an interesting idea for one more reason. We are
currently working on the update of pytest to version 8 and that version
no longer runs nose setup/teardown functions/methods which, as far as we
know now, is a change that breaks a lot of packages we previously
migrated