On 5/31/19 3:24 PM, Eduardo Habkost wrote: > Long story short: I would really like to drop support for Python > 2 in QEMU 4.1. > > What exactly prevents us from doing this? Does our deprecation > policy really apply to build dependencies? > Normally I'd say it's only nice to also follow the depreciation policy for tooling as well to give people a chance to switch away, but with regards to Python2, I feel like we're in the clear to drop it for the first release that will happen after the Python2 doomsday clock. (So, probably 4.2.) --js
- [Qemu-devel] Deprecation policy and build dependen... Eduardo Habkost
- Re: [Qemu-devel] Deprecation policy and build... John Snow
- Re: [Qemu-devel] Deprecation policy and b... Markus Armbruster
- Re: [Qemu-devel] Deprecation policy a... John Snow
- Re: [Qemu-devel] Deprecation poli... Cornelia Huck
- Re: [Qemu-devel] Deprecation... Eduardo Habkost
- Re: [Qemu-devel] Deprecation... Philippe Mathieu-Daudé
- Re: [Qemu-devel] Deprecation poli... Peter Maydell
- Re: [Qemu-devel] Deprecation... John Snow
- Re: [Qemu-devel] Depreca... Peter Maydell
- Re: [Qemu-devel] Dep... John Snow
- Re: [Qemu-devel] Dep... Markus Armbruster