Charles Hartman wrote:
> I'm getting really tired of not understanding this: Can someone point
> me to some single place that explains the whole path / PATH /
> PYTHONPATH arrangement for Python? I know there are two sorts on the
> Mac, framework and /usr, and I know some other bits and piece
On 6-mrt-2006, at 3:24, Bob Ippolito wrote:
>
> On Mar 5, 2006, at 5:56 PM, Zachary Pincus wrote:
>
>> Otherwise, Mac Python's bundle loading code should have a way to
>> expose the global symbol loading mechanism (necessary for C++ RTTI
>> with templates) to user code. There are two ways that I
On 7-mrt-2006, at 2:04, Zachary Pincus wrote:
> Hi folks,
>
> Despite the fact that dlopen() is available on OS X for 10.3 and
> above, the python dl module has not been made available on 10.3 and
> 10.4.
>
> Specifically, some code in the python setup.py script explicitly
> prevents the dl modul
I'm getting really tired of not understanding this: Can someone point
me to some single place that explains the whole path / PATH /
PYTHONPATH arrangement for Python? I know there are two sorts on the
Mac, framework and /usr, and I know some other bits and pieces, but I
have no clear overal
>> I think the Mac OS X box on the sourceforge compile farm may be 10.2.
Only if you're a developer on some SF project. Is there a python
project someone can add me to so I can test this (and the dl module)
patch? Or should I register some dummy project?
Zach
Thanks for your feedback, Bob.
>> I don't have access to a 10.2 machine currently, so if someone is
>> able to test this patch on 10.1, 10.2, and/or 10.3, I would be
>> most grateful. I can try to find some 10.2 install disks (and hope
>> that my computer can run 10.2) if nobody has easy acc
Hi folks,
Despite the fact that dlopen() is available on OS X for 10.3 and
above, the python dl module has not been made available on 10.3 and
10.4.
Specifically, some code in the python setup.py script explicitly
prevents the dl module from being built on darwin even if python sees
dlfcn
On 6-mrt-2006, at 20:47, Samuel M. Smith wrote:
> I find the search to be very helpful. Is it hard to convert from
> HTML to Apple Help format?
No, there's a script in the python tree to do the transformation.
There's
another script that compiles the search index, but that doesn't
reliab
I find the search to be very helpful. Is it hard to convert from HTML
to Apple Help format?
On 06 Mar, 2006, at 12:32, Ronald Oussoren wrote:
>
> On 6-mrt-2006, at 20:25, Charles Hartman wrote:
>
>> But the Mac Help program has always been and still is a dog. I'd
>> much rather have the HTML
On 6-mrt-2006, at 20:25, Charles Hartman wrote:
> But the Mac Help program has always been and still is a dog. I'd
> much rather have the HTML docs myself.
One advantage of the Mac Help program is that it has a search
function. IDLE's 'Help/Python Docs' just
opens a webbrowser. I am however
But the Mac Help program has always been and still is a dog. I'd much
rather have the HTML docs myself.
Charles
On Mar 6, 2006, at 11:23 AM, Ronald Oussoren wrote:
>
> On Monday, March 06, 2006, at 05:13PM, Samuel M. Smith
> <[EMAIL PROTECTED]> wrote:
>
>> I asked this before but no one re
On 6-mrt-2006, at 17:39, Brendan Simons wrote:
>
> --- Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>> On Monday, March 06, 2006, at 05:07PM, Brendan
>> Simons <[EMAIL PROTECTED]> wrote:
>
>>> I did some more digging in /system and /developer,
>> and
>>> found this icon:
>>
>> http://twototango.blo
So in an attempt to finally get rid of the potential morass that
further work on PyOXIDE could be, I'm release a very early version of
ScrIDE, a generic, extensible, scripting IDE. There are several
major differences between the two - first, ScrIDE is designed to
support multiple scripting
Thanks for the tips!
On Mar 6, 2006, at 9:52 AM, Dethe Elza wrote:
> Using XCode isn't really the best way to create PyObjC apps. The
> recommended way is to use InterfaceBuilder to create your UI,
> implement it with PyObjC, and use py2app to build the application from
> there.
>
> Check out
Using XCode isn't really the best way to create PyObjC apps. The
recommended way is to use InterfaceBuilder to create your UI,
implement it with PyObjC, and use py2app to build the application from
there.
Check out the tutorial on the PyObjC site, and the docs for py2app.
PyObjC tutorial: http:/
Following the simple example app that Apple provides for PyObjC has
lead me to a number of questions ... and a failed build. The example
demonstrates using Xcode & InterfaceBuilder to build a simple app,
PyAverager. My attempts at a build yield "Build failed for target
"Development" erro
On Mar 6, 2006, at 12:20 AM, Zachary Pincus wrote:
>>> (2) Move to using dlopen() to load the libraries instead of
>>> NSLinkImage. This might need some minor changes to
>>> dynload_shlib.c, and it would need the configure script to be
>>> smart enough to choose dynload_next.c on 10.2 and b
--- Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> On Monday, March 06, 2006, at 05:07PM, Brendan
> Simons <[EMAIL PROTECTED]> wrote:
> >I did some more digging in /system and /developer,
> and
> >found this icon:
>
>http://twototango.blogs.com/Developer_Applications_JavaTools_AppletLauncher.png
>
On Monday, March 06, 2006, at 05:13PM, Samuel M. Smith <[EMAIL PROTECTED]>
wrote:
>I asked this before but no one responded.
>Wouldn't it be a good idea to include the Python Reference docs in
>Mac Help format in the the
>MacPython universal installer? or at least as another package
The big
On Monday, March 06, 2006, at 05:07PM, Brendan Simons <[EMAIL PROTECTED]> wrote:
>
>--- Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>> Fine by me, if someone actually creates the icons!
>> Brendan Simons has created some icons that look good
>> enough, although the launcher icon could be better.
--- Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> Fine by me, if someone actually creates the icons!
> Brendan Simons has created some icons that look good
> enough, although the launcher icon could be better.
I did some more digging in /system and /developer, and
found this icon:
http://twotota
I asked this before but no one responded.
Wouldn't it be a good idea to include the Python Reference docs in
Mac Help format in the the
MacPython universal installer? or at least as another package
**
Samuel M. Smith Ph.D.
2966
On Monday, March 06, 2006, at 11:12AM, linda.s <[EMAIL PROTECTED]> wrote:
>what are the benefits of building python from source file?
>any difference if using installer?
I'd use the installer, that way you don't have to worry about depedencies like
readline and bsddb.
Ronald
>Linda
>___
On Monday, March 06, 2006, at 01:17PM, has <[EMAIL PROTECTED]> wrote:
>Donovan Preston wrote:
>
>>Stop with the 16 ton weight/snakes/apples debate. Just use the new,
>>official, python logo
>
>Absolutely agree, this is a solved problem already. It's not my most favourite
>logo design ever eithe
Donovan Preston wrote:
>Stop with the 16 ton weight/snakes/apples debate. Just use the new,
>official, python logo
Absolutely agree, this is a solved problem already. It's not my most favourite
logo design ever either (though still better than any others I've seen), but
that's irrelevant. Build
what are the benefits of building python from source file?
any difference if using installer?
Linda
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
>> (2) Move to using dlopen() to load the libraries instead of
>> NSLinkImage. This might need some minor changes to
>> dynload_shlib.c, and it would need the configure script to be
>> smart enough to choose dynload_next.c on 10.2 and below.
>
> If you come up with a patch for (2) against Pyt
27 matches
Mail list logo
