>(3) running 'make install' would not work since I had no permission to
>write in some directories. I don't fully understand this since
>I am the
>admin and I was running logged in as such, but to no avail.
>Solution: run this as
>
>sudo make install
>
>type in the password and you're of
I'm starting to build universal binaries for a bunch of 'nix stuff,
some of which have python bindings/extensions. Has anyone looked at
a universal Python framework? I'd hate to have to step backwards to
Apple's included Python framework for that, but I may have to.
-
William Kyngesbu
On 9-dec-2005, at 18:56, William Kyngesburye wrote:
> I'm starting to build universal binaries for a bunch of 'nix stuff,
> some of which have python bindings/extensions. Has anyone looked at
> a universal Python framework? I'd hate to have to step backwards to
> Apple's included Python framewo
On Dec 9, 2005, at 12:36 PM, Jack Jansen wrote:
>
> On 9-dec-2005, at 18:56, William Kyngesburye wrote:
>
>> I'm starting to build universal binaries for a bunch of 'nix stuff,
>> some of which have python bindings/extensions. Has anyone looked at
>> a universal Python framework? I'd hate to ha
On Dec 9, 2005, at 9:56 AM, William Kyngesburye wrote:
> I'm starting to build universal binaries for a bunch of 'nix stuff,
> some of which have python bindings/extensions. Has anyone looked at
> a universal Python framework? I'd hate to have to step backwards to
> Apple's included Python fram
What with one thing or another, that's how I've had to build
everything so far - build once for each and merge them. Tho with my
limited skills, I've taken a more rough approach - build ppc,
duplicate and clean, add in i386 options manually to makefiles,
build, merge using the same link co
It's much better to build PPC only if you can't test i386. If you
create a broken universal or i386 build, then your software doesn't
work on i386 machines. If you create a PPC-only build, it runs on
i386 machines.. just not optimally. Much better than broken.
-bob
On Dec 9, 2005, at 1:0
Hi! All
When I have module say module.py with sentance like
#!pythonw
import os
from appscript import *
and then import from terminal say pythonw, it show me
error or warning message
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/aem/send/errors.py:5:
On Dec 9, 2005, at 3:19 PM, Zhi Peng wrote:
> /System/Library/Frameworks/Python.framework/Versions/2.3/lib/
> python2.3/plat-mac/macerrors.py
> on line 326, but no encoding declared; see
> http://www.python.org/peps/pep-0263.html for details
> import macerrors
>
> But if I erased "from appscri
Thanks all I have to add #!pythonw # -*- coding: Latin-1 -*- at beginging of the file macerrors to get rid of warning message What was the difference when I try to install module say I have module.py on Macintosh? from distutils.core import setup setup(name="MyModule", version
On Dec 9, 2005, at 3:55 PM, Zhi Peng wrote:
> What was the difference when I try to install module say I have
> module.py on Macintosh?
>
> from distutils.core import setup
> setup(name="MyModule", version="1.0" py_modules=["module.py"])
>
>
> Is above enough to set up the module? Where are "mo
Bob
Let me say
Thanks a lot for your email
First, then I will read corresponding document.
Surely it helps a lot.
Regards
Zhi
--- Bob Ippolito <[EMAIL PROTECTED]> wrote:
>
> On Dec 9, 2005, at 3:55 PM, Zhi Peng wrote:
>
> > What was the difference when I try to install
> module say I ha
Hi! All In my c code, I have used myMod=PyImport_ImportModule("moduleName") and run on Mac, but it just can not import the "moduleName" for some unknown reason. I am sure I install the "moduleName" by "pythonw setup install". And I can import "moduleName" from command lines such as >
On Dec 9, 2005, at 4:41 PM, Zhi Peng wrote:
> In my c code, I have used myMod=PyImport_ImportModule("moduleName")
> and run on Mac, but it just can not import the "moduleName" for
> some unknown reason.
>
> I am sure I install the "moduleName" by "pythonw setup install".
> And I can import
Hi! Bob I have not tried to append current directory in sys.path. Maybe I need to do sth sys.path.append("./") and then do import. The module is installed in MacPython package. The os module is in python23.dylib so it can find it and import it. But my module is just a py file. Thanks
Well I have no idea whether you're extending or embedding Python..
and if you are embedding, I have no idea what steps you've taken to
initialize the interpreter... so I'm not sure.
Like I said before, what you need to do is make absolutely sure
you're using the correct Python interpreter, f
16 matches
Mail list logo
