Where is py5.__file__ set

[vsquared]

Any way to change the setting for py5.__file__?

[villares]

I think you got it backwards, when you do import py5 the Python interpreter tries to find the module, and when it succeeds py5.__file__ shows you where it is. No "setting" is possible. Your Python interpreter will look at the environment and will pick a py5 module according to the search procedure, I once heard a talk about it's intricacies, heavy stuff: https://docs.python.org/3/reference/import.html#searching

If you want to have different versions of py5 being imported at different times, you build different envs.
You mentioned on another post how much of a hassle it can be, "this envs thing", and I agree, but there is little we can do about it. Either the py5 user is advanced and builds their envs, or they are beginners and the easiest way I found to provide a consistent, isolated (important!) environment is by making them use Thonny...

[vsquared]

Can't destroy venv, Thonny refuses to run without it. However, my little editor uses miniconda3 like I want it to, but still won't run P2D or P3D in spite of having a refurbished py5 environment with a recent py5.jar untouched by me.

[villares]

My suggestion would be:
A) Try to make it work with module mode so you don't need Thonny, then you'll need to do a conda activate your-py5-env and then python editor.py.
B) Remove every Thonny trace and get a fresh Thonny (the env is it's "core" Python, it uses it itself and for your programs)
C) Point Thonny to use the miniconda3 interpreter (I had mixed results with this)
D) Don't stress about it and improve your editor in other directions... or study how Thonny works, for fun.

[vsquared]

I appreciate your suggestions and will keep it for future reference. In the meantime I put venv back like it was; I really don't care if Thonny uses it as long my editor uses miniconda3. I found some files that my editor wouldn't run (P3D); no error messages, just sits there. I felt like something was wrong with the editor until I tried the same file in Thonny and it wouldn't run it either, again no error messages. Then I didn't feel so bad, but have no idea why this occurs.

[villares]

Hmm, if P3D is failing in a fresh py5 release, it could be another issue... Can you check if P3D works on Processing Java?
(I have seen students with certain video cards / drivers silently refuse to work on P3D...)

[vsquared]

Following works in Processing 4.4.4

void setup(){
  size(400,400,P3D);  
}