hx2A
commented
2 years ago Update on the current situation:
- When run through the Jupyter (either the IPython kernel or the py5 kernel), users should use the
%gui osxmagic before importing py5. If you forget to use the magic it will be done for you and you will see a warning. py5 will work fine for OSX users for this case. - The
run_sketchcommand line utility uses the pyobjc library to perform the same sorcery that%gui osxdoes and makes py5 work on osx. Note that%gui osxis not available outside of Jupyter. py5 fill work fine for OSX users who are using therun_sketchutility. - Currenttly py5 does not work with the generic python interpreter on OSX because
gui osxis not available and the pyobjc stuff is not (yet) present. - Eventually I would like to use pyobjc for running py5 sketches anywhere on OSX, eliminating the need for
%gui osxentirely. This may not be possible though given what the IPython kernel already does for animation threads, but it also isn't that important, as calling%gui osxis not big deal. It should be possible to use pyojbc to get py5 working with the generic python interpreter. I have a partially working solution for this and will complete it at some point.
py5 doesn't work on OSX without using Jupyter and
%gui osxmagic. The sketch will be running but the window is not visible.run_sketchframe_countnumber will be increasing and the output of print statements will appearIdeally, py5 should work with a regular Python interpreter. I can live with the fact that the
%gui osxmagic is necessary when using Jupyter notebooks, but this leaves a dependency on Jupyter. Users may want to create a Python script to run a Sketch without having to use Jupyter.py5 uses JPype as the Python-Java bridge, and there is a known issue in JPype related to this. I believe this problem is dependent on a fix for this JPype issue.