I'm one of developers from a open source software named InVesalius
[1], it's using wxPython. In Mac OS X 10.6.3 (Snow Leopard) it runs
OK, but when I run it:
python invesalius.py
I got:
This program needs access to the screen.
Please run with 'pythonw', not 'python', and only when your are logged
in on the main display of your Mac.
I'm using virtualenv, the python comes from macports, and I have to
call python with "arch -i386 python" because it was compiled with
+universal variant. I try to run pythonw, but I'm using virtualenv and
"arch -i386 pythonw" gives me "arch: posix_spawnp: pythonw: Bad CPU
type in executable". So I google about this, some peoples tell that is
possible to run wxpython apps without pythonw, but I couldn't find
nothing about how to do that. Is it actually possible? The funny part
is that I can run wxpython app with ipython, so I think it's possible
to run without python, maybe I need to set some env variables.
You need to use a framework build of Python for wx to be able to access the GUI display. I think the macports build is just an ordinary unix build without the framework. If that is not correct then perhaps virtualenv is doing something that makes it not able to see the Python framework?
···
On 6/17/10 6:14 AM, Thiago Franco Moraes wrote:
Hi all,
I'm one of developers from a open source software named InVesalius
[1], it's using wxPython. In Mac OS X 10.6.3 (Snow Leopard) it runs
OK, but when I run it:
python invesalius.py
I got:
This program needs access to the screen.
Please run with 'pythonw', not 'python', and only when your are logged
in on the main display of your Mac.
I'm using virtualenv, the python comes from macports, and I have to
I don't know if virtualenv is doing something. I can use ipython to
run wxpython apps, and ipython is running over virtualenv. I compiled
wxpython with carbon support. Here the portfiles to compile wxpython:
On Jun 17, 2:48 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 6/17/10 6:14 AM, Thiago Franco Moraes wrote:
> Hi all,
> I'm one of developers from a open source software named InVesalius
> [1], it's using wxPython. In Mac OS X 10.6.3 (Snow Leopard) it runs
> OK, but when I run it:
> python invesalius.py
> I got:
> This program needs access to the screen.
> Please run with 'pythonw', not 'python', and only when your are logged
> in on the main display of your Mac.
> I'm using virtualenv, the python comes from macports, and I have to
You need to use a framework build of Python for wx to be able to access
the GUI display. I think the macports build is just an ordinary unix
build without the framework. If that is not correct then perhaps
virtualenv is doing something that makes it not able to see the Python
framework?
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
On Jun 18, 9:23 am, tfmoraes <totonixs...@gmail.com> wrote:
On Jun 17, 2:48 pm, Robin Dunn <ro...@alldunn.com> wrote:
> On 6/17/10 6:14 AM, Thiago Franco Moraes wrote:
> > Hi all,
> > I'm one of developers from a open source software named InVesalius
> > [1], it's using wxPython. In Mac OS X 10.6.3 (Snow Leopard) it runs
> > OK, but when I run it:
> > python invesalius.py
> > I got:
> > This program needs access to the screen.
> > Please run with 'pythonw', not 'python', and only when your are logged
> > in on the main display of your Mac.
> > I'm using virtualenv, the python comes from macports, and I have to
> You need to use a framework build of Python for wx to be able to access
> the GUI display. I think the macports build is just an ordinary unix
> build without the framework. If that is not correct then perhaps
> virtualenv is doing something that makes it not able to see the Python
> framework?
> --
> Robin Dunn
> Software Craftsmanhttp://wxPython.org
Hi,
I don't know if virtualenv is doing something. I can use ipython to
run wxpython apps, and ipython is running over virtualenv. I compiled
wxpython with carbon support. Here the portfiles to compile wxpython: