| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
It seems like 3.4 and 3.5 are 100% compatible, and most ebuilds involving python in some way tolerate them both (any-of ( python_targets_python3_3 python_targets_python3_4 python_targets_python3_5)). Yet there are some that are still unhappy with 3.5. This makes me really annoyed and I was wondering if it was possible to write a simple script to add python_targets_python3_5 where needed. Would this break anything, and if no, why can't the maintainers or some portage-tree admin do it? |
| 5 |
|
| 6 |
Of course there might be some other barrier to adopting 3.5 that I can't understand, so please explain it to me. |
| 7 |
-----BEGIN PGP SIGNATURE----- |
| 8 |
Version: GnuPG v2 |
| 9 |
|
| 10 |
iQEcBAEBCAAGBQJWnPGDAAoJEBYxB87Vey/RIAsH/A56lGenSnQhgBY3ItZZV+10 |
| 11 |
YkrtLo+k9miSWlSB6QI0KPRkIRJU2ldnT89gYQ2FeUqOrSwVdMcUuDdWnbOpktk5 |
| 12 |
6QBn7E3sLGHb19JznhF3SkuSjf2IhzFz28cVo7D1vG8wL9hTip1J5DQuw+q9dz9F |
| 13 |
63T4qwepiKSrHMIKIsJaP/dMBZO8Ic0+/0mgYW5huhrSX0pKSHktMGaAIlU12bSs |
| 14 |
wFUI+uCQjAvGsHtikJJJVBvLEnuSeMiJNvlSzMfe94JXZ+27b+qYjvZ2gJTsDRUO |
| 15 |
QnIhAppF+enKcQzaAQNxCzbti2gCEg5Y3vNX25zoqAYfgC21sxDZsyhytV++Mis= |
| 16 |
=2xVk |
| 17 |
-----END PGP SIGNATURE----- |
Archives