> Pretty much -- to access the Mac GUI, an app needs to be in a proper Mac
> application bundle. The Framework build supplies that. Technically, the use
> of a framework is independent for this requirement, but using a Framework
> build is the easiest way to satisfy it.
OK.
> Do you have a reason
Hi,
I seem to recall that a Framework build of Python is needed if you
want to do anything with the native Mac GUI. Is my understanding
correct? If so, is this requirement documented somewhere?
Thanks!
Brian
___
Pythonmac-SIG maillist - Pythonmac-S
I think this is currently the best approach because PYTHONPATH gets
lost in sudo commands in Leopard.
On 11/1/07, Jack Jansen <[EMAIL PROTECTED]> wrote:
>
> On 1-Nov-2007, at 20:45 , Brian Granger wrote:
> > Running python setup.py install on Leopard causes packages to be
&g
gt; > Defaultsenv_keep += "PYTHONPATH"
> >
> >
> >
> > But that would involve editing a file in /etc as root.
> > Straightforward enough, but likely to get overwritten and what if
> > the user screws this up?
> >
> >
>
sen:
>
> >
> > On 1-Nov-2007, at 20:45 , Brian Granger wrote:
> >> Running python setup.py install on Leopard causes packages to be
> >> installed in the usual:
> >>
> >> /Library/Python/2.5/site-packages
> >>
> >> But, Apple put
Hi,
In the process of working through the issues with sys.path on Leopard,
I have found another potential Leopard bug that is particularly nasty.
In Tiger, sudo preserves environment variables:
$ export FOO=/tmp
$ python -c "import os; print os.environ['FOO']"
/tmp
$ sudo python -c "import os; p
This is definitely worth looking at for this type of thing. Thanks
for the pointer.
Brian
On 11/2/07, Kent Johnson <[EMAIL PROTECTED]> wrote:
> Christopher Barker wrote:
> > I suppose this may be a time to take a good look at workingenv again...
>
> Or virtualenv which has replaced workingenv:
>
On 11/1/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > > It's not entirely silly. This has been the advice given to app
> > > developers on this list and the PyObjC list for years now. It's nice
> > > to have a better system Python for quick scripts, but it's still the
> > > System Python. It's
> It's not entirely silly. This has been the advice given to app
> developers on this list and the PyObjC list for years now. It's nice
> to have a better system Python for quick scripts, but it's still the
> System Python. It's Apples, for their stuff that uses Python. And it
> is specific to
Hi,
I have been playing around with python on Leopard today. Overall, I
am very pleased, but I just ran into a problem that will affect a
large number of users.
In Leopard, Apple includes a number of python packages in:
ls /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/pyth
I am afraid that this patch won't cut it. It does a simple test of
the os type. The problem is that someone could install a version of
python on OS X and want to use the other readline library (for example
the OS X python binaries from the python.org website ship with this
readline). Somehow, we
The rlineimpl.py module is the place in python where readline gets
imported. I would look there and also I would look to see where
ipython is doing its equivalent of parse_and_bind.
Brian
On 10/26/07, Noah Gift <[EMAIL PROTECTED]> wrote:
> Ed,
>
> You are a genius! Thanks, I totally forgot you t
I am forwarding this to the ipython-dev list. A number of the core
ipython dev's use OS X, so we will surely jump on this one as soon as
we get our hands on Leopard. This (libedit support) is great news as
it has been one of the main problems with the built-in Python on OS X
for a long time.
Che
Hi,
We need to deploy a qt4 based python app and I am working on some of
the build issues. Because we are using Qt, we need a framework build
of Python (we are using 2.5). One of our requirements is that users
can build and use the app without doing a system wide install.
I am worried that our
Sorry I didn't see this one earlier. Using the --mpi option to build
mpi4py is not the recommended way of building it. The docs are a
little out of date on this one. The following should work:
python setup.py build --mpicc=path_to_your_mpicc_executable
Let me know if that works! I build mpi4p
> If you want to make full use of multiple processors using pure python
> code you'll have to use multiple processes.
This is absolutely true, but in practice it is a little more
complicated. If you can factor your algorithm so that each process
can be run completely separately, with no interproc
et me know.
Brian Granger
[EMAIL PROTECTED]
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
What version of gcc are you using? I have not had any luck getting
scipy and its dependencies working with gcc 4.0.
Maybe this has changed? Has anyone had success with gcc 4.0 yet?
If you need to change the default version of gcc on Mac OS X use the
command:
sudo gcc_select 3.3
Brian
On
at:
http://hammonds.scu.edu/~classes/pyxg.html
Apple's description of Xgrid is at:
http://www.apple.com/server/macosx/features/xgrid.html
Brian Granger
Brian E. Granger
Assistant Professor of Physics
Santa Clara University
[EMAIL PROTECTED]
Phone: 408-551-1891
Fa
19 matches
Mail list logo
