| 1 |
On Wed, 2021-08-04 at 20:27 +0100, Sergei Trofimovich wrote: |
| 2 |
> On Tue, 03 Aug 2021 11:15:13 +0200 |
| 3 |
> Michał Górny <mgorny@g.o> wrote: |
| 4 |
> |
| 5 |
> > Hi, everyone. |
| 6 |
> > |
| 7 |
> > Just a quick note: I've pushed Python 3.10.0rc1 today. It has many last |
| 8 |
> > minute changes that can break packages that were ported to previous |
| 9 |
> > 3.10.0 betas before. |
| 10 |
> > |
| 11 |
> > For practical reasons, we're going to support only >=3.10.0_rc1 going |
| 12 |
> > forward. If your package fails with >=3.10.0_rc1, feel free to apply |
| 13 |
> > fixes without caring for backwards compatibility with betas. If you see |
| 14 |
> > failures with 3.10.0_beta4, please try upgrading to _rc1 first. |
| 15 |
> > |
| 16 |
> > Notably, the newest releases of dev-python/django and dev-python/sphinx |
| 17 |
> > that I've pushed today were updated for _rc1 and will have failures with |
| 18 |
> > _beta4. |
| 19 |
> |
| 20 |
> Should we drop PYTHON_COMPAT=python3_10 for known to break package versions? |
| 21 |
> For example latest stable dev-python/sphinx-4.0.3 did not like today's ~arch |
| 22 |
> python: |
| 23 |
|
| 24 |
I suppose that's fine if it doesn't break depgraph. For completeness, |
| 25 |
the newer sphinx version is fixed for that. |
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives