1 |
Hi, everyone. |
2 |
|
3 |
We're a fair bit behind with updating packages to support Python 3.5 |
4 |
[1,2]. I've been doing some testing-and-adding myself lately. Sadly, I |
5 |
have to say that what was supposed to be a pretty simple experience |
6 |
turned out a bumpy fix-a-lot-of-mistakes road. |
7 |
|
8 |
Unlike what some people claim, updating PYTHON_COMPAT is not a problem. |
9 |
Neither should be testing the changes. The major problem is bad quality |
10 |
of multiple ebuilds that require immediate attention before python3.5 |
11 |
can be even added. The biggest issue is lack of tests. |
12 |
|
13 |
While I can agree that sometimes tests in Python packages are poorly |
14 |
written upstream or not present at all, there's a lot of packages where |
15 |
lack of tests is purely the Gentoo maintainer's fault, and once added |
16 |
they work seamlessly. |
17 |
|
18 |
So if you have some time, please take a look at our Python packages, |
19 |
especially those on the list for 3.5 testing ([1]), and enable test |
20 |
support whenever possible. Even partially failing tests are better than |
21 |
none. |
22 |
|
23 |
In the matter of instructions, I would like to remind you that distutils |
24 |
don't have a single method of running tests. Some upstreams support |
25 |
the setuptools 'test' command, some require using specific test systems. |
26 |
Some tips regarding the common cases can be found on [3]. |
27 |
|
28 |
If you decide to add 3.5 to packages, please also test 3.6 to avoid |
29 |
revisiting the package again soon. If the new implementations fail, |
30 |
preferably please file a bug to ensure that we can track it. |
31 |
|
32 |
Thanks in advance! Please also let me know if you can think of some ways |
33 |
to improve our documentation. |
34 |
|
35 |
[1]:https://qa-reports.gentoo.org/output/gpyutils/34-to-35.txt |
36 |
[2]:https://qa-reports.gentoo.org/output/gpyutils/34-to-35.svg |
37 |
[3]:https://wiki.gentoo.org/wiki/Project:Python/Tests |
38 |
|
39 |
-- |
40 |
Best regards, |
41 |
Michał Górny |