Hi Thomas, Benjamin, and Python Team, Thomas Grainger <tagr...@gmail.com> writes:
> Awesome, thanks for the update! Just to let you know there's a pre-release > https://pypi.org/project/modernize/0.9rc0/ version that combines the > libmodernize and modernize namespace Good to know! I'm not familiar with the details, but it sounds like either the "modernize" or "python3-modernize" Debian package will need to be removed from src:modernize for versions >= 0.9rc0 (the remaining packages would need a "Provides:removed-package" in debian/control). This would mean that src:modernize would need to pass through the NEW queue again. https://ftp-master.debian.org/new.html As you can see, there's a bit of a backlog! Any packages that need to pass through NEW need to do so before 2021-02-12. I'm hopeful that fissix will be reviewed and accepted before then, thus enabling an update to Modernize 0.8.0, and I recommend preparing an upload well before then (even though we can't upload until fissix clears NEW) After the 0.8.0 upload has been prepared, work could commence on updating the Modernize for Debian to 0.9rc0. If 0.9.0 (final release) is not released early enough for it to pass through NEW, at least we'll have 0.8.0 in Bullseye (Debian 11). Alternatively, while the semantics are wrong, I wonder if it would be acceptable to use a dummy transitional package to avoid a trip through NEW? My feeling is it wouldn't be acceptable, but I could be wrong. And yes, unfortunately if fissix doesn't clear NEW before the soft-freeze deadline then we won't see a new Modernize release in a Debian stable release before Bookworm (Debian 12). Regards, Nicholas
