blob: 455efe1bb4b337c32fa8a98d8167593c3deba077 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
socket: 0.699
device: 0.692
files: 0.659
architecture: 0.641
user-level: 0.636
kernel: 0.634
network: 0.634
ppc: 0.630
performance: 0.626
PID: 0.613
register: 0.600
permissions: 0.592
mistranslation: 0.570
semantic: 0.570
graphic: 0.566
risc-v: 0.550
hypervisor: 0.524
peripherals: 0.503
arm: 0.502
boot: 0.496
vnc: 0.487
x86: 0.487
VMM: 0.476
TCG: 0.470
KVM: 0.461
i386: 0.456
virtual: 0.450
debug: 0.441
assembly: 0.378
Support Python 3 to build
Currently qemu's configure requires Python 2 to build. As Python 2 is rapidly approaching its EOL, it should be possible to build qemu with Python 3.
Python 2 EOL is in 2020 so there is a fair amount of time.
QEMU is transitioning to support both Python 2.6+ and 3 but most Python code has not been converted yet.
You are welcome to contribute patches:
https://wiki.qemu.org/index.php/Contribute/SubmitAPatch
> Python 2 EOL is in 2020 so there is a fair amount of time.
Not as much time as you might think. Even well before that time, any new releases of long life and/or enterprise distros are likely to choose to skip py2 by default, as it will be EOL long before the distro itself EOLs.
Two patches series posted in Aug last year:
https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg03642.html
https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg06528.html
An updated series covering both of those, and also turning on tests
https://lists.gnu.org/archive/html/qemu-devel/2018-01/msg02978.html
The series mentioned in comment #3 was merged in v2.12.0, see commit c21965a0c8b979c306e927f158257e5b0fa3a1f9.
|
