Re: [Pythonmac-SIG] pychecker

2005-01-03 Thread Robert Kern
Bob Ippolito wrote: On Jan 3, 2005, at 11:58 PM, Robert Kern wrote: Okay. At some point, that symlink got blown away on my machine, so I put in the install-*lib entries. If that symlink got blown away, /Library/Python/2.3 shouldn't have ended up in sys.path (unless you jigger that in elsewhere

Re: [Pythonmac-SIG] pychecker

2005-01-03 Thread Bob Ippolito
On Jan 3, 2005, at 11:58 PM, Robert Kern wrote: Bob Ippolito wrote: Do this instead: # Begin File [install] install-scripts=/usr/local/bin install-data=/usr/local/share # End File Screwing with purelib and platlib is a terrible idea if you ever have multiple versions of Python installed, because t

Re: [Pythonmac-SIG] pychecker

2005-01-03 Thread Robert Kern
Bob Ippolito wrote: Do this instead: # Begin File [install] install-scripts=/usr/local/bin install-data=/usr/local/share # End File Screwing with purelib and platlib is a terrible idea if you ever have multiple versions of Python installed, because they will all use the same .pydistutils.cfg. Th

Re: [Pythonmac-SIG] pychecker

2005-01-03 Thread Bob Ippolito
On Jan 3, 2005, at 10:25 PM, Robert Kern wrote: Mike Hansen wrote: Does anyone have any ideas on how I can get pychecker to work? Create a file in your home directory called .pydistutils.cfg (yes, the first dot is important). Put the following text (between the two #-comment lines) into it: # Beg

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Andrew P. Lentvorski, Jr.
On Jan 2, 2005, at 11:16 PM, Tim Peters wrote: [Bob Ippolito] However, it is our (in the "I know you use Windows but I am not the only one that uses Mac OS X sense) problem so long as Darwin is a supported platform, because it is highly unlikely that Apple will backport any "fix" to the allocato

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Guido van Rossum
Coming late to this thread. I don't see the point of lying awake at night worrying about potential memory losses unless you've heard someone complain about it. As Tim has been trying to explain, here are plenty of other things in Python that we *could* speed up if there was a need; since every spe

Re: [Pythonmac-SIG] pychecker

2005-01-03 Thread Robert Kern
Mike Hansen wrote: I'm having trouble getting pychecker to work in OS X 10.3.7 I installed it and don't recall seeing any error messages. In the terminal when I type pychecker myprogram.py -bash: pychecker: command not found I noticed in the pythonmac faq, it mentioned that many disutils packages

[Pythonmac-SIG] pychecker

2005-01-03 Thread Mike Hansen
I'm having trouble getting pychecker to work in OS X 10.3.7 I installed it and don't recall seeing any error messages. In the terminal when I type pychecker myprogram.py -bash: pychecker: command not found I noticed in the pythonmac faq, it mentioned that many disutils packages install into /Syste

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Tim Peters
[Bob Ippolito] > ... > What about for list objects that are big at some point, then > progressively shrink, but happen to stick around for a while? An > "event queue" that got clogged for some reason and then became stable? It's less plausible that we''re going to see a lot of these simultaneousl

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Bob Ippolito
On Jan 3, 2005, at 4:49 PM, Tim Peters wrote: [Tim Peters] Ya, I understood that. My conclusion was that Darwin's realloc() implementation isn't production-quality. So it goes. [Bob Ippolito] Whatever that means. Well, it means what it said. The C standard says nothing about performance metrics

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Tim Peters
[Tim Peters] >> Ya, I understood that. My conclusion was that Darwin's realloc() >> implementation isn't production-quality. So it goes. [Bob Ippolito] > Whatever that means. Well, it means what it said. The C standard says nothing about performance metrics of any kind, and a production-qualit

[Pythonmac-SIG] Problems with matplotlib

2005-01-03 Thread Larry Meyn
Has anyone had problems with installing and using matplotlib under OS X? I've tried installing the last couple of versions and while installation goes smoothly it crashes when I try to import from pylab, as shown below >>> from pylab import * Traceback (most recent call last): File "", line

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Bob Ippolito
On Jan 3, 2005, at 11:15 AM, Guido van Rossum wrote: Coming late to this thread. I don't see the point of lying awake at night worrying about potential memory losses unless you've heard someone complain about it. As Tim has been trying to explain, here are plenty of other things in Python that we *

[Pythonmac-SIG] Live fast, die young: testers wanted for new MacPython additions

2005-01-03 Thread Jack Jansen
Folks, I have a first version of the next "MacPython additions for 10.3" available. Please give it a try, including test-driving the Package Manager (which has gone up to version 0.5, and has had all the packages updated to newer versions). Report here with any problems you find, and also if

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Bob Ippolito
On Jan 3, 2005, at 2:16 AM, Tim Peters wrote: [Bob Ippolito] ... Your expectation is not correct for Darwin's memory allocation scheme. It seems that Darwin creates allocations of immutable size. The only way ANY part of an allocation will ever be used by ANYTHING else is if free() is called with

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Tim Peters
[Bob Ippolito] > ... > Your expectation is not correct for Darwin's memory allocation scheme. > It seems that Darwin creates allocations of immutable size. The only > way ANY part of an allocation will ever be used by ANYTHING else is if > free() is called with that allocation. Ya, I understood t

[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations

2005-01-03 Thread Tim Peters
[Bob Ippolito] > Quite a few notable places in the Python sources expect realloc(...) to > relinquish some memory if the requested size is smaller than the > currently allocated size. I don't know what "relinquish some memory" means. If it means something like "returns memory to the OS, so that t