Re: [gentoo-dev] Reverse use of Python/Ruby versions

["William L. Thomson Jr." <wlt-ml@o-sinc.com>]

[-- Attachment #1: Type: text/plain, Size: 2754 bytes --]

On Tue, 11 Apr 2017 00:44:30 +0300
Mart Raudsepp <leio@gentoo.org> wrote:

> Ühel kenal päeval, E, 10.04.2017 kell 17:33, kirjutas William L.
> Thomson Jr.:
> > Add a new Java version and recompiling packages with it, will also
> > immediately show breakage if any.
> > 
> > If your saying Python code is of higher quality than Java. I would
> > digress heavily on that. You have leniency in python not being
> > strong typed. Lack of generics and stuff could only mean that could
> > be worse.
> > Relying on internals to handle data types for you.  
> 
> Which is why python modules can't just pretend to work with a newer
> python by merely happening to "compile" and install. It is not
> strongly typed and it does not involve a AOT phase (pyc is just a
> semi-binary representation of the source code really) and issues are
> not found unless properly tested at runtime or test suite.

Java is strong typed. Lots things in Java have tests. That does not
ensure no bugs. Nor does that mean things are the same all the time.

Case in point. I have issues that upstream does not. Both on JDK 1.8,
and java is java so it should be the same right? 

Fix for Java 1.8 and Guice 4.1
https://github.com/jclouds/jclouds/pull/1036

Its likely a matter of dependencies. Their guice may not have been
compiled as Java 1.8. Thus I may be triggering something they are not.
It is not easily figured out if the fix is needed or not. Though in my
case without it fails. In their case without it does not fail....

> > Regardless of new eclass, the TARGETS remain. Things did not change
> > from a user perspective. Recently packaging some ebuilds, the
> > COMPAT/VERSION does not seem to have changed. Despite what ever
> > changes to the eclass.  
> 
> Users don't get unexpected failures, as things that are claimed to
> work with a given python version, probably actually do so. 

This really is no different. We are not talking about a new python
version going straight to stable. Any issues would be in ~arch, and
short of speculation. It may not effect as many packages as people
think.

If python is really breaking that much between even 3.x releases. Then
just shows that much more how it sucks. Though I think breakage could
be looked out for. Code modified. Fixes sent upstream. etc.

When I see lots of versions. Seems more like people are maintaining vs
fixing/patching the code and sending stuff upstream. I would have more
but not everything do I take upstream. Depends on if I feel they will
be receptive or a waste of my time.

Thankfully most in Java are forward looking. Most active projects
already support 1.8 and have things being tested under Java 9.

-- 
William L. Thomson Jr.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]