Replies: 1 comment 4 replies
-
|
What do I need to do to reproduce this? If I create a Windows directory with some non-ascii characters, put the JVM in a subdirectory, set JAVA_HOME, I would not be able to start jpype? Can I reproduce this on my Windows machine?
This warning should be in py5, not the plugin. Someone might be using py5 outside of Thonny. Those users are also exposed to this problem. I would rather take a stab at fixing it though. What Thrameos wrote in that thread might be enough to get me started. |
Beta Was this translation helpful? Give feedback.
-
|
Cool, yes, putting the JVM on a subdir with non-ascii characters in the path (example: |
Beta Was this translation helpful? Give feedback.
-
|
I'll give it a try then! |
Beta Was this translation helpful? Give feedback.
-
|
@hx2A this has been fixed at Update: Not that fast. They had no new releases since December 2023 😢 |
Beta Was this translation helpful? Give feedback.
-
Right, the latest version, 1.5.0 I believe, has been out for months. I just looked at that repo to see if a release was coming soon and I didn't see anything. Typically they have an open issue with a checklist you can follow to know how soon the release will take place. |
Beta Was this translation helpful? Give feedback.
-
I had recently other "international" students with non-ascii usernames on Windows that struggled to make py5 work, they had no idea of what was going on, as the message just communicates the JVM coudn't be started... I was lucky to remember this might have been the issue. I wonder how many people silently give up on it :(
jpype-project/jpype#1111
Perhaps we could we add a warning message on the plug-in if it detects the JAVA_HOME path contains non-ascii chars in order to mitigate this issue while it is not fixed?
Beta Was this translation helpful? Give feedback.
All reactions