| 1 |
Ühel kenal päeval, E, 10.04.2017 kell 17:33, kirjutas William L. |
| 2 |
Thomson Jr.: |
| 3 |
> Add a new Java version and recompiling packages with it, will also |
| 4 |
> immediately show breakage if any. |
| 5 |
> |
| 6 |
> If your saying Python code is of higher quality than Java. I would |
| 7 |
> digress heavily on that. You have leniency in python not being strong |
| 8 |
> typed. Lack of generics and stuff could only mean that could be |
| 9 |
> worse. |
| 10 |
> Relying on internals to handle data types for you. |
| 11 |
|
| 12 |
Which is why python modules can't just pretend to work with a newer |
| 13 |
python by merely happening to "compile" and install. It is not strongly |
| 14 |
typed and it does not involve a AOT phase (pyc is just a semi-binary |
| 15 |
representation of the source code really) and issues are not found |
| 16 |
unless properly tested at runtime or test suite. |
| 17 |
|
| 18 |
> Regardless of new eclass, the TARGETS remain. Things did not change |
| 19 |
> from a user perspective. Recently packaging some ebuilds, the |
| 20 |
> COMPAT/VERSION does not seem to have changed. Despite what ever |
| 21 |
> changes to the eclass. |
| 22 |
|
| 23 |
Users don't get unexpected failures, as things that are claimed to work |
| 24 |
with a given python version, probably actually do so. |
Archives