Re: py27-wxpython-* not working
On Sat, Apr 30, 2016 at 7:10 PM, Brandon Allbery wrote: > it's prone to tell you what a *new* shell will see --- not what your > *current* shell is doing, because shells cache what they've already seen I should mention that it is possible to make the shell forget what it's seen: "hash -r" in most shells, "rehash" in *csh. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: py27-wxpython-* not working
On 1 May 2016 at 01:10, Brandon Allbery wrote: > > (b) what does "type python" return? ("which" can lie. Specifically, it's > prone to tell you what a *new* shell will see --- not what your *current* > shell is doing, because shells cache what they've already seen. If you ran > "port select --set" in that shell and it had already seen /usr/bin/python, > it will be running that still when you run "python"; "which" may not show > this, "type" will.) You can indeed try /opt/local/bin/python2.7 -c 'import wx' and then perhaps also port contents py27-wxpython-3.0 just in case to double check that the wx module is indeed there. You should have lots of files under /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/wx-3.0-osx_cocoa/wx "port select --set wxWidgets ..." shouldn't have any influence, but "port select --set python ..." does influence the python that gets executed, so that might be relevant. Mojca ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: py27-wxpython-* not working
On Sat, Apr 30, 2016 at 7:05 PM, Neil Voss wrote: > # which python > /opt/local/bin/python > (a) what does "port select --show python" return? (b) what does "type python" return? ("which" can lie. Specifically, it's prone to tell you what a *new* shell will see --- not what your *current* shell is doing, because shells cache what they've already seen. If you ran "port select --set" in that shell and it had already seen /usr/bin/python, it will be running that still when you run "python"; "which" may not show this, "type" will.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
py27-wxpython-* not working
I cannot get wxPython to work on my mac. I have tried installing all of the available ports (py27-wxpython-2.8, py27-wxpython-3.0), to no avail. I keep getting 'ImportError: No module named wx' Can you provide me any tips to debug this? Google has not been helpful. Relevant code below: MacBook Pro (Retina 13-inch, Late 2013) OS X El Capitan, v 10.11.4 # sudo port installed | grep -i wx mkvtoolnix @7.9.0_0+wxwidgets (active) py27-wxpython-3.0 @3.0.2.0_0 (active) wxPython-3.0 @3.0.2_5 (active) wxWidgets-3.0 @3.0.2_4 (active) wxWidgets-common @3.1.0_0 (active) wxWidgets_select @1.0_1 (active)# sudo port select --set wxWidgets wxWidgets-3.0 Selecting 'wxWidgets-3.0' for 'wxWidgets' succeeded. 'wxWidgets-3.0' is now active. # python -c 'import wx' Traceback (most recent call last): File "", line 1, in ImportError: No module named wx # which python /opt/local/bin/python # python -V Python 2.7.10 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users