How to run wxPython with the python.org installer on macOS 12.4 (Monterey)

wxPython Users
#1

I asked this question on stackoverflow but probably should have asked here:

I want to install python from python.org and have it work with wxPython in a terminal on macOS:

  • Install python 3.9.13 using the macOS 64-bit universal2 installer
  • Install wxPython using pip - pip3 install -U wxPython
  • Start python in a shell and try and fire up a wx app:
DB0837:~ andypiper$ /Library/Frameworks/Python.framework/Versions/3.9/bin/python3
Python 3.9.13 (v3.9.13:6de2ca5339, May 17 2022, 11:37:23) 
[Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx
>>> wx.App()
This program needs access to the screen. Please run with a
Framework build of python, and only when you are logged in
on the main display of your Mac.

Please don’t point me at brew or pyenv or anaconda or framework builds - I want the above combination to work, and it seems not to. The download from python.org is a framework build and if I run this from IDLE it works fine using the exact same version of python, so it feels like it must be some macOS security issue or shell/python interaction. I have read lots and lots of posts with the same error but different environmental setup. Thanks for any help.

Wxpython stops working on macOS 12.6.1: framework build error
#2

It should work. I almost exclusively use the stock builds from Python.org. When you run those commands are you using a native local terminal or something like ssh or other remote access to the machine?

Also, please try again with the newest build.

#3

I’m using a native terminal. I tried with the newest build. I feel like something is messed up in my environment, but cannot figure out what it is.

#4

So I tried the fix here: https://stackoverflow.com/a/73386418/5325222 - and it worked! So I reckon this is actually a bug in wxPython, but what the cause is who can say.

#5

It may be some kind of security feature, but I haven’t been able to duplicate the issue using essentially the same environment as you. I used a venv, and macOS 12.1 instead of 12.4, but I would not expect those differences alone to trigger this bug.

See this screen capture video.

#6

I’m suspect the difference between 12.1 and 12.4 is the problem. This used to work for me, but no longer - but I am not sure at what point it stopped as there are multiple python versions at play here.

#7

image
image1698×872 161 KB