On Thu, 2021-05-06 at 09:31 +0200, Michał Górny wrote: > Hi, > > As you have probably noticed, the first Python 3.10.0 beta has landed > (which means no major changes anymore, only bug fixes), and I've started > adding python3.10 target to various packages. So far I've managed to > reach pytest which is a good sign but there are still many broken > (upstream) packages. > > You can try porting some low-hanging fruit already but please note > the following: > > 1. The target is stable-masked and won't be stable for at least another > half a year (final 3.10.0 release is planned in September). > > 2. Remember to test packages. In my very short experience, 3.10 breaks > more stuff than 3.9 or 3.8 did (but then, I've started testing earlier). > > 3. Do *not* revbump when adding 3.10. It's stable-masked, so you don't > have to worry about breaking stable. > > 4. If you're about to bump what looks like low-hanging fruit, it's > a good idea to try porting the current version first. More versions > with py3.10 support to choose from, less problems later on. Though > I suppose it doesn't matter much given that it won't go stable in a few > months. > > 5. If stuff fails, try upstream's VCS -- there might be some easy > backports available. > > 6. Note that urllib3 is not yet ready which means a significant portion > of packages is blocked anyway. > > If you have any problems, feel free to ping me. >
Oh, and if you're using pkgcheck, it will give you a PythonCompatUpdate result if the package in question has all the deps ready. -- Best regards, Michał Górny
