Closed hroncok closed 8 months ago
Please report this again once 3.13 beta is released, if it's still an issue.
Huh. You have it right here. Happy to retest with betas, but I don't understand the closure.
There's not really a need to report this. We'll enable 3.13 test env once it's in beta or rc phase, at which point we'll see these failures if they're still happening. You're welcome to report them if you're also planning to submit a fix at the same time, but otherwise it just creates a placeholder that's not useful to us. Alpha is also way too early to start reporting this, as it's not stable yet and so doesn't indicate what we may actually need to fix.
Hello, in Fedora, we are trying to test Python 3.13 early to discover problems in Python itself and in important packages in the Python ecosystem.
With 3.13.0a1, we see some of the jinja's tests failing. I haven't got into investigating the failures just yet, but I decided to open this issue here. I understand that jinja is not expected to work on a first alpha release of Python out of the box, but I assume you are interested in knowing this.
To reproduce, clone this repository and run
tox -e py313
.(I used tox 3, so I needed to add
isolated_build = True
to the tox config. I assume this is not needed with tox 4.)Environment: