On Thu, Dec 19, 2019 at 04:30:25PM -0000, Dimitri John Ledkov wrote:
> Should I quickly force cdimage to use python3? And like upgrade it to
> bionic?
No. I said I hate that we're doing it, but note that I approved, merged,
and deployed this anyway.
But the cdimage code itself has been bilingual for a while, and it should be
possible to switch the codebase to python3 now on the existing xenial host.
I would've been in favor of doing this now, except ubuntu-archive-tools is
*not* python3-safe and there are other commands calling into
isotracker.py/qatracker.py in that code base which would need porting first.
> I guess we could refactor cdimage to not use qatracker as a library, but
> call it as a binary. Then we could keep qatracker as python3.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
<email address hidden> <email address hidden>
On Thu, Dec 19, 2019 at 04:30:25PM -0000, Dimitri John Ledkov wrote:
> Should I quickly force cdimage to use python3? And like upgrade it to
> bionic?
No. I said I hate that we're doing it, but note that I approved, merged,
and deployed this anyway.
But the cdimage code itself has been bilingual for a while, and it should be archive- tools is py/qatracker. py in that code base which would need porting first.
possible to switch the codebase to python3 now on the existing xenial host.
I would've been in favor of doing this now, except ubuntu-
*not* python3-safe and there are other commands calling into
isotracker.
> I guess we could refactor cdimage to not use qatracker as a library, but
> call it as a binary. Then we could keep qatracker as python3.
-- /www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https:/
<email address hidden> <email address hidden>