So it's a bit more clear to me re Java 6 vs Java 7. Basically for OS X only, Java 6 support continues without requiring getting a support contract. In particular, on my OS X laptop, I have a current Java 6 release when I switch my Java home accordingly:

$ java -version
java version "1.6.0_51"

(I usually run Java 7 of course.)

Having said that, I think it makes sense for us to move to Java 7 where it will plug specific bugs and gaps; experience has shown that it can be a lot easier for us to make pip and other applications work than trying to push changes upstream.

After then figuring this out on Java 7, we can then also selectively downgrade this capability, eg os.O_NOFOLLOW is available only on Java 7.This means pip doesn't work, but easy_install should. However, this requires a bit more workaround, so Java 6 support won't necessarily be immediately available in trunk as we make this transition.

Thoughts?

- Jim




On Sun, Sep 1, 2013 at 3:38 AM, Nick Rothwell <nick@cassiel.com> wrote:
On 31/08/2013 18:18, Matthew.Webber@Diamond.ac.uk wrote:
>> Java 7 is 64-bit only, so I wouldn't be able to load a Java 7 JVM into a
>> 32-bit hosting app.
> That's not correct; Java 7 is available for 32 and 64 bit Windows and Linux..
Sure; I'm on OS X, where Java 7 is 64-bit only.

     -- N.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Jython-users mailing list
Jython-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jython-users