| 1 |
On 09/04/2017 23:44, Kristian Fiskerstrand wrote: |
| 2 |
> On 04/09/2017 06:15 PM, William L. Thomson Jr. wrote: |
| 3 |
>> Not sure if this is practical, it may be less work if the use of |
| 4 |
>> Python and Ruby versions ( maybe others ) is reversed. Rather than |
| 5 |
>> adding all the versions that the ebuild supports. What if it only |
| 6 |
>> included versions it did not support? |
| 7 |
> It would only work if upstream provide a strong assurance for forward |
| 8 |
> compatibility. Explicit testing and marking working seems the only |
| 9 |
> practical way to ensure stability. |
| 10 |
Surely enough forward compatibility may be a problem and python |
| 11 |
upstream does deprecate and remove features #1 and things that fiddle |
| 12 |
with python bytecode will easily break. |
| 13 |
However we keep $KEYWORDS between version of the same package and that |
| 14 |
it's subject to the same exact kind of problems. |
| 15 |
|
| 16 |
Honestly just trying out python 3.6 is a pain at the moment and the |
| 17 |
situation is the same at every python bump. |
| 18 |
|
| 19 |
#1 https://docs.python.org/3/whatsnew/index.html |
Archives