New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jspawnhelper in the cave application bundle on Mac is not executable #95

Closed
jaredwsmith opened this Issue Dec 21, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@jaredwsmith
Contributor

jaredwsmith commented Dec 21, 2016

When trying to set up PyDev in an effort to get derived parameters working, I repeatedly got the message that spawning the Python interpreter failed.

I did some digging and found that this issue can creep up if jspawnhelper is not executable for whatever reason. Here is an answer from another Java project that led me down the right path: http://stackoverflow.com/a/31015371

Sure enough, this ended up being the problem. After manually making jspawnhelper within the Mac application bundle executable, I'm able to add Python interpreters as needed.

@live4right

This comment has been minimized.

live4right commented Dec 21, 2016

Hey Jared,
Is there a similar component on the Windows version too? I have been trying to get the PyDev to point to my Python installation so I can get at least the wind data (barbs, streamlines) to display, but it hasn't worked out too well. It goes through 1,836 lines of code and it acts like the python isn't there. Let me know if you can get those derived parameters figured out for the Windows version if you have the time and let me know how to set things up right. Thanks

--Carl

@mjames-upc

This comment has been minimized.

Member

mjames-upc commented Dec 21, 2016

Thanks for letting me know about this, Jared, I'll look at it shortly.

@jaredwsmith

This comment has been minimized.

Contributor

jaredwsmith commented Jul 13, 2017

Still seeing this in 17.1.1 when I set up PyDev or work with localizations, just FYI. Same steps fix it with the new app bundle.

@mjames-upc

This comment has been minimized.

Member

mjames-upc commented Jul 13, 2017

Known issue being addressed for 17.1.1-2

@mjames-upc mjames-upc closed this Jul 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment