El Wednesday, 14 de May de 2008 22:00:10 Kevin Walzer escribió:
> Most likely, no. py2app works all kinds of magic in creating an
> application bundle, including rolling in the Python standard library,
> whatever GUI tookit you are using, and other scripts, and it runs
> Mac-specific tools to modif
On May 14, 2008, at 2:43 PM, Michael VanLandingham wrote:
gcc on the command line or makefile, then you need to add the right
flags so that it can find the framework
The Python framework that ships with OS X is already in the search
path, so all you'd need is
-framework Python
added t
If you're using Xcode, you just #include in your
source file, then add the Python framework to your project (in Xcode,
right click on your project file in the "Groups & Files" pane, select
"Add->Existing Frameworks..."). You might need to configure the build
rules to make sure the right v
Arne Babenhauserheide wrote:
El Wednesday, 14 de May de 2008 19:57:29 Kevin Walzer escribió:
Copying repsonse to the list so others can see the follow-up:
sorry...
Arne Babenhauserheide wrote:
Wouldn't it be possible to just include a binary Mac Python and then copy
the script to the corre
El Wednesday, 14 de May de 2008 19:57:29 Kevin Walzer escribió:
> Copying repsonse to the list so others can see the follow-up:
sorry...
> Arne Babenhauserheide wrote:
> > Wouldn't it be possible to just include a binary Mac Python and then copy
> > the script to the correct location?
>
> No, no
Copying repsonse to the list so others can see the follow-up:
Arne Babenhauserheide wrote:
El Tuesday, 13 de May de 2008 20:46:46 Kevin Walzer escribió:
If all you are distributing are Python scripts, you can already to this
with distutils or setuptools.
I'd do it, if most Mac Users where com
At 10:53 +0100 2008/04/05, Matthias Baas wrote:
>Just for the record, the distutils have a function that returns the include
>path:
> >>>import distutils.sysconfig
> >>>distutils.sysconfig.get_python_inc()
>
>So if you really need to know the include path for some reason, you should us
I've just moved all my stuff from a Intel Imac on 10.4.11 to a Macpro
on 10.5.2. On both machines I have the same universal activestate
python (both 2.5.1 and 2.5.2.2 give the same problem). I have some
codes in fortran from which I build a shared library using f2py from
numpy. Now when I i
