py27-wxpython-* not working

Mojca Miklavec mojca at
Sat Apr 30 16:28:18 PDT 2016

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


"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.


More information about the macports-users mailing list