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 mo
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"
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
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:
MacBoo
