Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Ronald Oussoren
On Oct 2, 2006, at 11:12 PM, Bob Ippolito wrote: That's a good point, just the same. Now if just put a copy of easy_install in the standard MacPython installer, we'd be one step in the right direction. That would deviate from the norm where MacPython ships only with what comes with Python --

Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Ronald Oussoren
On Oct 2, 2006, at 9:24 PM, Bob Ippolito wrote: PyObjC, wxPython, Tk, all need to be installed correctly before they can be used. On 10.4 Tk is already installed and could be used, it has appearently has issues but an egg frontend could be kept simple enough to work around those. Bu

Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Bob Ippolito
On 10/2/06, Christopher Barker <[EMAIL PROTECTED]> wrote: > Bob Ippolito wrote: > > It's not a great idea to put a front-end on easy_install at this > > point. It would be an enormous amount of work for very little gain. > > It's also not at all designed such that it's easy to break what it's > > d

Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Christopher Barker
Bob Ippolito wrote: > It's not a great idea to put a front-end on easy_install at this > point. It would be an enormous amount of work for very little gain. > It's also not at all designed such that it's easy to break what it's > doing up into little chunks so that you can properly display status >

Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Bob Ippolito
On 10/2/06, Christopher Barker <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > >>> What I was looking for is actually a bit more modest: I want to > >>> create an installer that checks that all dependencies are fulfilled. > > > True, but I don't mind. The users I am thinking of know nothing

Re: [Pythonmac-SIG] Problems with MacPython packages at pythonmac.org - numpy, scipy, matplotlib

2006-10-02 Thread Christopher Barker
Adam Bull wrote: > Hi, I'm told this is the right place to discuss problems with the > packages at pythonmac.org? There are a few things that need fixing: > > The supplied version of scipy, 1.5.0, doesn't work with the supplied > version of of numpy, 1.0b5; it gives an error when importing.

Re: [Pythonmac-SIG] building statically with bdist_mpkg

2006-10-02 Thread Christopher Barker
[EMAIL PROTECTED] wrote: > I've looked around for some docs on how to do this, but was > unsuccessful: How do you build statically using bdist_mpkg? At the > moment, I am building manually using > > python setup.py config -L ../staticlibs build install > > where staticlibs holds all of the li

Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython

2006-10-02 Thread Christopher Barker
[EMAIL PROTECTED] wrote: >>> What I was looking for is actually a bit more modest: I want to >>> create an installer that checks that all dependencies are fulfilled. > True, but I don't mind. The users I am thinking of know nothing about > Python and would just install packages. I want to be abl

Re: [Pythonmac-SIG] Are python extensions compatible between 32 and 64 bit Macs?

2006-10-02 Thread Bob Ippolito
On 10/2/06, Russell E. Owen <[EMAIL PROTECTED]> wrote: > Will C extensions to Python that are built on 64 bit Macs (such as the > new iMacs) will work on 32 bit Macs, and visa versa? Definitely if the universal binary distribution for Python 2.5 or 2.4.3 are used, because it explicitly compiles fo

[Pythonmac-SIG] Are python extensions compatible between 32 and 64 bit Macs?

2006-10-02 Thread Russell E. Owen
Will C extensions to Python that are built on 64 bit Macs (such as the new iMacs) will work on 32 bit Macs, and visa versa? -- Russell ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig