[Pythonmac-SIG] hello and a first question for everyone...

[David Cairns]

hi all... at WWDC and i decided to join the SIG.

also, i was wondering if anyone has gotten PyOpenGL and/or
OpenGLContext to work in tiger (albeit under X11).  if not, then what
is the best way to go about establishing a context to associate with
python ?

thanks in advance!

 -- david
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] ActiveState's OS X Python

[Nick Matsakis]

>> What do you think if Apple's (somewhat schizo, mind you) usage of
>> /Library/Python/X.Y/[site-packages/] ? This would solve that issue.

> and probably cause others.. I'd rather leave that location to Apple.
> If it turns out that it's really a good idea to put something there,
> then we can change it for 2.5.

That locations _isn't_ for Apple---it's for third-party additions.  If it
is possible to build extensions that will work with Apple's Python,
ActivePython, and MacPython (with the same major version), then /Library
would be a great place to put such extensions.  (same with ~/Library).

It certainly seems possible for MacPython 2.3 and Apple Python.

Nick
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] [Matplotlib-users] Re: matplotlib on Tiger?

[Chris Barker]

Charles Moad wrote:
> Installing each
> dependency would probably be just as easy as trying to use components
> from my installer.

I put instructions for how to do this in my package for OS-X-10.3,
py2.3.0. Here they are. If you do all this, you can donate the package
to Bob's repository on pythonmac.org.

There is a related thread about defining a standard way to do this for
matplotlib, so it will build out of the box.

They should work just fine for newer versions of OS, matplotlib, and
python. Sorry they are a bit wordy:

Installing matplotlib on OS-X (10.3.7)

Here are my notes as to what it took to get matplotlib (0.71) installed
and working on OS-X. I have so far kept a fink-free system, so that's
what I've done here as well. I use it with the AGG back end for
generating images for a web site, and hopefully with the wx backend for
interactive use and embedding in wx Applications. I've also quickly got
it working with TK. Note that this is kind of a running commentary, not
well edited. I'd read the whole thing before starting.

1) Requirements:
---
According to the matplotlib install docs
(http://matplotlib.sourceforge.net/installing.html), you need the following:

freetype (>= 2.1.7)
libpng
zlib

Personally, I've been avoiding Fink, as it doesn't seem to play well
with the rest of OS-X, including the Apple supplied Python, so I've
looked elsewhere for these libs.

a) Freetype:
I seem to have it in:

/usr/X11R6/include/freetype2

I don't think I installed it myself, so it probably came with Apple's
X11, Which I did install.

However, I seemed to be having problems with that version, so I looked,
and it seems to be:

libfreetype.6.3.dylib

Given that freetype2 is currently at version 2.1.9, I have no idea what
to make of that! So off to sourceforge to get a new freetype:

http://freetype.sourceforge.net/index2.html

where I got:

freetype-2.1.9.tar.gz

Following the instructions in docs/INSTALL.UNX:

$ ./configure
$ make
$ sudo make install

That puts it in /usr/local/..., which is a good place for it.

NOTE: The above will build  freetype as a shared library, which is fine
if you are building ot run on the same system you are building on.
However, if you want to buuild a re-distributable package, you'll need a
static library, which you can get by doing:

$ ./configure --disable-shared --enable static
$ make
$ sudo make install

Hmm. that made the static libs (*.a) , but also the dynamic ones.



Make sure to do:
$ make clean

if you had already built it. You may also have to remove the shared
libs, so that they won't be found (*.dyld). I had to remove them from
/usr/local/lib.

b) zlib:
I have:
/usr/include/zlib.h

I don't know where I might have gotten it, but there it is.

NOTE: I checked on another system in my office, and it doesn't have
zlib. It does, however have libz, which I am told is the same thing, to
you shouldn't need this.

c) libpng:
This, I didn't have on my system, except inside the wxWidgets source
tree, so I went looking for it.

Note that you need zlib to compile libpng, so make sure you have that first.

I did a google search for "libpng OS-X". I found:

http://www.libpng.org/pub/png/pngcode.html

Which led me to the libpng sourceforge site.

 From there I downloaded:

libpng-1.2.8.tar.gz

unpacked it, and opened a terminal in the libpng-1.2.8 directory, and did:

$ cp scripts/makefile.darwin ./makefile

(note that according to the INSTALL, there is supposed to be a
makefile.macosx, but it wasn't there)

I took a look in the makefile, and found:

ZLIBLIB=/usr/local/lib
ZLIBINC=/usr/local/include

Which is not where zlib is on my system. However, while I can find
zlib.h, I couldn't fine the actual lib, so I tried make without changing
anything.

$ make

Which seemed to work fine. zlib must be installed in a standard
location, and gcc  found it.

$ sudo make install

to install the lib into /usr/local/ (this was specified in the makefile,
and it's a good place for it)

$ make test
and
$ ./pngtest pngnow.png

Which both seemed to pass.

If you want to build a re-distributable version of matplotlib, you need
the static version of libpng, instead of the dynamic one. It doesn't use
./configure, so instead, I did a:

sudo make install-static

and that installed the *.a files in /usr/local/lib.

d) Numeric or numarray:

I already have Numeric installed, from Bob Ippolito's PIMP (MacPython
Package Manager) repostitory. (www.undefined.org/python)

2) Building matplotlib
-
First, I took a look at the matplotlib setup.py. It had "auto" for the
back-end flags, so I thought I would give it a try that way:

$python setup.py build

If you have only the static version of libpng and libfreetype (*.a, and
not *.dylib) in /usr/local/lib (or anywhere else on your lib search
path), then it should link those statically.

That worked!
$ sudo python setup.py install

4) And now to test!

$python

>>> import py

Re: [Pythonmac-SIG] [Matplotlib-users] Re: matplotlib on Tiger?

[Chris Barker]

Charles Moad wrote:
> Installing each
> dependency would probably be just as easy as trying to use components
> from my installer.

I put instructions for how to do this in my package for OS-X-10.3, 
py2.3.0. Here they are. If you do all this, you can donate the package 
to Bob's repository on pythonmac.org.

There is a related thread about defining a standard way to do this for 
matplotlib, so it will build out of the box.

They should work just fine for newer versions of OS, matplotlib, and 
python. Sorry they are a bit wordy:

Installing matplotlib on OS-X (10.3.7)

Here are my notes as to what it took to get matplotlib (0.71) installed 
and working on OS-X. I have so far kept a fink-free system, so that's 
what I've done here as well. I use it with the AGG back end for 
generating images for a web site, and hopefully with the wx backend for 
interactive use and embedding in wx Applications. I've also quickly got 
it working with TK. Note that this is kind of a running commentary, not 
well edited. I'd read the whole thing before starting.

1) Requirements:
---
According to the matplotlib install docs 
(http://matplotlib.sourceforge.net/installing.html), you need the following:

freetype (>= 2.1.7)
libpng
zlib

Personally, I've been avoiding Fink, as it doesn't seem to play well 
with the rest of OS-X, including the Apple supplied Python, so I've 
looked elsewhere for these libs.

a) Freetype:
I seem to have it in:

/usr/X11R6/include/freetype2

I don't think I installed it myself, so it probably came with Apple's 
X11, Which I did install.

However, I seemed to be having problems with that version, so I looked, 
and it seems to be:

libfreetype.6.3.dylib

Given that freetype2 is currently at version 2.1.9, I have no idea what 
to make of that! So off to sourceforge to get a new freetype:

http://freetype.sourceforge.net/index2.html

where I got:

freetype-2.1.9.tar.gz

Following the instructions in docs/INSTALL.UNX:

$ ./configure
$ make
$ sudo make install

That puts it in /usr/local/..., which is a good place for it.

NOTE: The above will build  freetype as a shared library, which is fine 
if you are building ot run on the same system you are building on. 
However, if you want to buuild a re-distributable package, you'll need a 
static library, which you can get by doing:

$ ./configure --disable-shared --enable static
$ make
$ sudo make install

Hmm. that made the static libs (*.a) , but also the dynamic ones.



Make sure to do:
$ make clean

if you had already built it. You may also have to remove the shared 
libs, so that they won't be found (*.dyld). I had to remove them from 
/usr/local/lib.

b) zlib:
I have:
/usr/include/zlib.h

I don't know where I might have gotten it, but there it is.

NOTE: I checked on another system in my office, and it doesn't have 
zlib. It does, however have libz, which I am told is the same thing, to 
you shouldn't need this.

c) libpng:
This, I didn't have on my system, except inside the wxWidgets source 
tree, so I went looking for it.

Note that you need zlib to compile libpng, so make sure you have that first.

I did a google search for "libpng OS-X". I found:

http://www.libpng.org/pub/png/pngcode.html

Which led me to the libpng sourceforge site.

 From there I downloaded:

libpng-1.2.8.tar.gz

unpacked it, and opened a terminal in the libpng-1.2.8 directory, and did:

$ cp scripts/makefile.darwin ./makefile

(note that according to the INSTALL, there is supposed to be a 
makefile.macosx, but it wasn't there)

I took a look in the makefile, and found:

ZLIBLIB=/usr/local/lib
ZLIBINC=/usr/local/include

Which is not where zlib is on my system. However, while I can find 
zlib.h, I couldn't fine the actual lib, so I tried make without changing 
anything.

$ make

Which seemed to work fine. zlib must be installed in a standard 
location, and gcc  found it.

$ sudo make install

to install the lib into /usr/local/ (this was specified in the makefile, 
and it's a good place for it)

$ make test
and
$ ./pngtest pngnow.png

Which both seemed to pass.

If you want to build a re-distributable version of matplotlib, you need 
the static version of libpng, instead of the dynamic one. It doesn't use 
./configure, so instead, I did a:

sudo make install-static

and that installed the *.a files in /usr/local/lib.

d) Numeric or numarray:

I already have Numeric installed, from Bob Ippolito's PIMP (MacPython 
Package Manager) repostitory. (www.undefined.org/python)

2) Building matplotlib
-
First, I took a look at the matplotlib setup.py. It had "auto" for the 
back-end flags, so I thought I would give it a try that way:

$python setup.py build

If you have only the static version of libpng and libfreetype (*.a, and 
not *.dylib) in /usr/local/lib (or anywhere else on your lib search 
path), then it should link those statically.

That worked!
$ sudo python setup.py install

4) And n

Re: [Pythonmac-SIG] [Visualpython-users] Re: avoid dueling pythons on tiger

[Dethe Elza]

On 7-Jun-05, at 7:16 PM, Jon Schull wrote:


> Thanks I have done that (by adding " set path = (/usr/local/bin  
> $path)" to  .tcshrc) and all is well.
>
> Now, as momentary liaison between the  pythonmac and vpython lists  
> I'll mention that VPython (a truly beautiful thing) could be made  
> independent of  X11 if someone from this group knew how to liberate  
> it...
>

I took a stab at it once, before VPython was refactored into C++, but  
I was still pretty new to OS X programming at the time, and it  
defeated me.  I haven't yet taken a look at the C++ version, it's on  
my todo list, but not a high priority right now.  I'd love to see  
VPython on OS X properly, but my hobby coding time is pretty limited  
right now.

--Dethe

"Well I've wrestled with reality for thirty-five years now, doctor,  
and I'm
happy to state I've finally won out over it." -- Elwood P. Dowd, Harvey


___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] [Visualpython-users] Re: avoid dueling pythons on tiger

[Jon Schull]

Thanks I have done that (by adding " set path = (/usr/local/bin $path)" to  .tcshrc) and all is well.Now, as momentary liaison between the  pythonmac and vpython lists I'll mention that VPython (a truly beautiful thing) could be made independent of  X11 if someone from this group knew how to liberate it...On Jun 7, 2005, at 10:16 AM, Bruce Sherwood [who maintains VPython] wrote:Maybe a Mac expert will step forward and make a version of Visual that can be driven by the native Mac Python? After all, OpenGL doesn't need X11, it's just that lacking Mac-specific expertise the only way we could get VPython running on Mac OSX was to piggyback off the Linux/Unix version. What is needed is really just one file, equivalent to wgl.cpp which handles Windows aspects (creating the graphics window, handling keyset and moust inputs, etc.). Is there anyone in the VPython commmunity who could write macgl.cpp?On Tue, 2005-06-07 at 11:54 -0400, Jon Schull wrote:That would be a very big step forward in lots of waysIs it clear that this requires understanding of VPython internals?Only somewhat.  The platform-specific parts of VPython are fairlylimited; the hardest part is probably learning the OSX GUI APIs.You would need to write implementations of glContext and glFont(declared in glcontext.h).  You will probably also need to write aplatmac.{cpp,h} files that contains all of the functionality present inplat{linux,win}.{cpp,h}.  You should be able to get a considerableamount of reuse from the platlinux.{h,cpp} files.  If there is anyambiguity about the responsibilities of these classes, I'll be happy tohelp out anyone who would be doing this work.I would recommend using the Carbon or Core Platform C interfaces ratherthan Cocoa via Objective-C++.-Jonathan=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Jon Schull, Ph.D.Associate ProfessorInformation TechnologyRochester Institute of Technology102 Lomb Memorial DriveRochester, New York 14623[EMAIL PROTECTED] 585-738-6696 On Jun 7, 2005, at 9:53 PM, Bob Ippolito wrote:On Jun 6, 2005, at 8:59 PM, Jon Schull wrote: Please forgive the cross-post.   I think this is a cross group issue.I've newly installed Tiger and would like to avoid the dueling pythons problem that plagued me with 0SX 10.3.  It would be nice to be running just one python, but I suppose that would be asking too much?I installed Bob's MacPython 2.4.1 from http://undefined.org/python/Double clicking the apps works fine.  But when I type "python" from terminal I get python Apple's python 2.3.5.   I'm sure this is obvious to many, but I'm also sure I'm not the only person who starts getting uneasy at this point.  So before I go too deep, I thought I'd askIs there a "right" way to be using just one (or just two) pythons and avoid conflicts? Put /usr/local/bin before /usr/bin on your PATH.  The default PATH includes ONLY Apple-installed components.  This is an "issue" with any third party software that has a command-line interface, as they all (should be, anyway) install to /usr/local/bin.-bob---This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotputa projector? How fast can you ride your desk chair down the office luge track?If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20___Visualpython-users mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/visualpython-users ___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] macpython on future apple's intel processors?

[Russell Finn]

On 6/8/05, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> It should be possible to split the configure script into two parts:
> one that tests cpu features (sizeof(int), byte order, ...) and one
> that tests API features (do we have sockets, ...). The cpu-features
> part can be converted to something that uses feature macros instead
> of detection, e.g.
> 
> #if defined __i386__
> #define LITTLE_ENDIAN
> ...
> #elif defined __ppc__
> #define BIG_ENDIAN
> ...
> #elif ...
> ...

It looks like Apple has anticipated you here
:

"If you are compiling a project that uses autoconf and trying to build
it for both the PowerPC and x86 architectures, you need to make sure
that when the project configures itself, it doesn't use autoconf
macros to determine the endian type of the runtime system. For
example, if your project uses the autoconf AC_C_BIGENDIAN macro, the
program won't work correctly when it is run on the opposite
architecture from the one you are targeting when you configure the
project. To correctly build for both PowerPC and x86 architectures,
use the compiler-defined __BIG_ENDIAN__ and __LITTLE_ENDIAN__ macros
in your code."

Apparently these symbols are already defined for you by gcc. (I'm
still trying to find exactly where it says so in the Apple
documentation.)

-- Russell Finn
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

[Pythonmac-SIG] Python on Mac OS X (WWDC2005 Session 613)

[Bob Ippolito]

The web presence for the Python on Mac OS X session at WWDC2005 is  
now up:  http://pythonmac.org/wwdc2005/

The CodeImporter example and slides will be available as soon as I've  
made sure that it's OK to post them.

-bob

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] matplotlib on Tiger---and Panther, with Py2.3 and Py2.4...

[Chris Barker]

John Hunter wrote:
> If either of you have a diff against setup*.py that will make mpl src
> builds on these systems work better, I'll fold them into the main
> line.

I had intended to do this, but before I do, I think theres a need for a 
little discussion.

Charles and I have taken two different approaches to dealing with the 
dependencies not included in stock OS-X:

libpng
libfreetype

(as noted by Charles, libfreetype does seem to exist, in some form with 
Apple's X11 implementation, but neither of us could get it to work)

The way I handled these libs was to build them as static libs, install 
them inside the matplotlib build tree, then alter the setup.py so that 
it would use the statically linked versions. This resulted in a simple 
stand-alone binary, that is easy to install. However, you do need to put 
those static libs in the right place before you can build, so I wasn't 
sure we'd want to hard-code that into the stock setup.py. You do need to 
resolve the dependencies in some way in any case, so maybe it's not a 
bad idea.

My understanding is that Charles took an alternative approach: providing 
libpng and libfreetype as OS-X Frameworks, and building matplotlib 
against those. This is really the way it "should" be done on OS-X. 
However, it seems a little harder to set up to me (unless the libs in 
question work with  a --framework flag to make. I spend a lot more time 
on Linux, so all this is a bit of a mystery to me.) It also strikes me 
as a little harder to make a package out of, as you've got multiple 
things to install and bdist_mpkg won't just do it for you.

What are other's thoughts about the best way to do this? It would be 
nice to have a standard approach built into the matplotlib setup.py.

-Chris

-- 
Christopher Barker, Ph.D.
Oceanographer

NOAA/OR&R/HAZMAT (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115   (206) 526-6317   main reception

[EMAIL PROTECTED]
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] macpython on future apple's intel processors?

[Ronald Oussoren]

On 7-jun-2005, at 22:45, Bob Ippolito wrote:

>
> On Jun 7, 2005, at 6:50 PM, Ronald Oussoren wrote:
>
>
>>
>> On 7-jun-2005, at 10:59, Bob Ippolito wrote:
>>
>>
>>
>>
>>>
>>> On Jun 7, 2005, at 12:36 AM, Markus Weissmann wrote:
>>>
>>>
>>>
>>>
>>>
 I think this won't be a big headache for the Python community - not
 even for
 the whole open source people; in fact - as darwin for x86  
 already is
 available
 for some time now - we've already tested some software on darwin/ 
 x86.
 You may find a list of RPMs I've built in end of 2004 for  
 opendarwin
 for Intel
 here [1]. Just check for the py_* named packages and relax! :)




>>>
>>> That's totally not true, though.  Basically, almost NONE of the Mac-
>>> specific Python stuff works correctly on Mac OS X for Intel, and the
>>> changes required to fix that are hard.
>>>
>>>
>>>
>>
>> Maybe, maybe not. I've quite optimistic about PyObjC (except the  
>> inject part,
>> but that's because I'm not interested in that feature).
>>
>
> It's still a considerable amount of work to beat libffi into using  
> the sysv ABI with the exception or two that Apple has made, and  
> then get it to configure and compile BOTH ways at the same time.

Getting libffi to work on Intel was easy enough, the hard part was  
understanding the libffi code. Getting it to build a fat library will  
be harder. I'm thinking of ripping the entire autoconf layer out, and  
might in the long term even convert libffi to something that's more  
pyobjc specific. We're currently converting python arguments to  
libffi argument arrays and those are then converted to stack frames.  
The smells like an inefficient code path.

>
> Fixing mach_inject (in the homogenous architecture case) is MUCH  
> less work. and it should probably even be possible to make it work  
> for both PPC and Intel even if the injector and injectee  
> architecture differ... though that would be a fair amount of  
> additional work.

I looked at the mach_inject code in the hotel. It contained a lot  
less architecture-specific code than I had expected. I might even  
attempt a port to Intel this week. Cross-platform injection makes my  
head hurt :-)

>
>
>> The hard part will be the creation of fat binaries.
>>
>
> Yeah.

It shouldn't be too hard, libffi will probably be the hardest part.  
It should be possible to split the configure script into two parts:  
one that tests cpu features (sizeof(int), byte order, ...) and one  
that tests API features (do we have sockets, ...). The cpu-features  
part can be converted to something that uses feature macros instead  
of detection, e.g.

#if defined __i386__
#define LITTLE_ENDIAN
...
#elif defined __ppc__
#define BIG_ENDIAN
...
#elif ...
...

API features should be the same across architectures.

>
> BTW:  Nearly all bundlebuilder apps are broken on Mac OS X for  
> Intel, and all py2app apps work (via Rosetta, anyway).

Only the standalone ones work, --semi-standalone apps that use / 
System/Library/Frameworks/Python.framework will most likely not work  
(pyobjc for ppc in a python with an intel image).

Ronald
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] avoid dueling pythons on tiger

[Ronald Oussoren]

On 6-jun-2005, at 20:59, Jon Schull wrote:

> Please forgive the cross-post.   I think this is a cross group issue.
>
> I've newly installed Tiger and would like to avoid the dueling  
> pythons problem that plagued me with 0SX 10.3.  It would be nice to  
> be running just one python, but I suppose that would be asking too  
> much?
>
> I installed Bob's MacPython 2.4.1 from http://undefined.org/python/
> Double clicking the apps works fine.  But when I type "python" from  
> terminal I get python Apple's python 2.3.5.   I'm sure this is  
> obvious to many, but I'm also sure I'm not the only person who  
> starts getting uneasy at this point.  So before I go too deep, I  
> thought I'd ask

You should add /usr/local/bin to the start of the search path of  
you're shell. If you're using bash (the default on Panther and Tiger)  
you can add these lines to .profile or .bash_profile in your home  
directory:

 export PATH
 PATH="/usr/local/bin:${PATH}"

 export MANPATH
 MANPATH="/usr/local/man:${MANPATH}"

This way the python in /usr/local/bin is seen before the system one.

Ronald

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] ActiveState's OS X Python

[Trent Mick]

> >>One tool that would be nice is something that will migrate site-
> >>packages from one to the other when you're switching.
> >>
> >
> >What do you think if Apple's (somewhat schizo, mind you) usage of
> >/Library/Python/X.Y/[site-packages/]
> >? This would solve that issue.
> 
> and probably cause others.. I'd rather leave that location to Apple.   
> If it turns out that it's really a good idea to put something there,  
> then we can change it for 2.5.

Cool. After I sent that I realized it could cause confusion for the
"naive user copying the whole framework" that you mentioned.

Trent

-- 
Trent Mick
[EMAIL PROTECTED]
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] ActiveState's OS X Python

[Bob Ippolito]

On Jun 8, 2005, at 12:30 AM, Trent Mick wrote:

> [Bob Ippolito wrote]
>
>> One tool that would be nice is something that will migrate site-
>> packages from one to the other when you're switching.
>>
>
> What do you think if Apple's (somewhat schizo, mind you) usage of
> /Library/Python/X.Y/[site-packages/]
> ? This would solve that issue.

and probably cause others.. I'd rather leave that location to Apple.   
If it turns out that it's really a good idea to put something there,  
then we can change it for 2.5.

-bob

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] retrieving config values from the System Preferences

[Antoine Pitrou]

Hi,

Thanks Nicholas and Doug for your answers. I will try both methods and
choose the most appropriate ;)

Regards

Antoine.


Le mardi 07 juin 2005 à 10:06 -0500, Nicholas Riley a écrit :
> On Tue, Jun 07, 2005 at 02:54:12PM +0200, Antoine Pitrou wrote:
> > I'm porting an app to Mac OS X and I need to retrieve the configuration
> > values entered in the System Preferences (specifically the HTTP proxy
> > settings). I already know how to do that under Gnome and Windows, but I
> > haven't found how to retrieve those values under Mac OS X (Panther, by
> > the way). Is there a reliable way to do that ?
> 
> Generic information is here:
> 
> 
> 


___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] ActiveState's OS X Python

[Trent Mick]

[Bob Ippolito wrote]
> One tool that would be nice is something that will migrate site- 
> packages from one to the other when you're switching.

What do you think if Apple's (somewhat schizo, mind you) usage of
/Library/Python/X.Y/[site-packages/]
? This would solve that issue.

Trent

-- 
Trent Mick
[EMAIL PROTECTED]
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] Py2App on Mactel with pygame?

[Bob Ippolito]

On Jun 8, 2005, at 12:14 AM, Keith Nemitz wrote:

>
> On Jun 7, 2005, at 10:45 PM, [EMAIL PROTECTED] wrote:
>
>
>>
>> BTW:  Nearly all bundlebuilder apps are broken on Mac OS X for Intel,
>> and all py2app apps work (via Rosetta, anyway).
>
> Will the altivec enhancements made to pygame 1.7 work in a py2app app?

I don't quite understand the point of this question?  Why would  
py2app have anything to do with AltiVec?

If you're asking "do applications built using the AltiVec-enabled SDL  
work on Mac OS X for Intel" then the answer is yes, but Rosetta  
doesn't support AltiVec so the code path will be the same as that of  
the G3.  I haven't tested any pygame apps specifically, but Frozen  
Bubble (SDL, Perl) worked fine (under Rosetta) and several PyObjC  
applications I've tested also work fine.

-bob

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

[Pythonmac-SIG] Py2App on Mactel with pygame?

[Keith Nemitz]

On Jun 7, 2005, at 10:45 PM, [EMAIL PROTECTED] wrote:

>
> BTW:  Nearly all bundlebuilder apps are broken on Mac OS X for Intel, 
> and all py2app apps work (via Rosetta, anyway).
>
> -bob
>
Bob,

Will the altivec enhancements made to pygame 1.7 work in a py2app app?

Keith Nemitz

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig