On 2-jan-05, at 4:40, Bob Ippolito wrote:
+SCRIPT="""#!/bin/sh
+export MACOSX_DEPLOYMENT_TARGET=10.3
+exec %s "[EMAIL PROTECTED]"
This script should check to see if MACOSX_DEPLOYMENT_TARGET is already
set. If I have some reason to set MACOSX_DEPLOYMENT_TARGET=10.4 for
compilation (say I'm compil
On Jan 2, 2005, at 4:28 PM, Jack Jansen wrote:
On 2-jan-05, at 4:40, Bob Ippolito wrote:
+SCRIPT="""#!/bin/sh
+export MACOSX_DEPLOYMENT_TARGET=10.3
+exec %s "[EMAIL PROTECTED]"
This script should check to see if MACOSX_DEPLOYMENT_TARGET is
already set. If I have some reason to set
MACOSX_DEPLOYM
On 2-jan-05, at 22:35, Bob Ippolito wrote:
On 2-jan-05, at 4:40, Bob Ippolito wrote:
+SCRIPT="""#!/bin/sh
+export MACOSX_DEPLOYMENT_TARGET=10.3
+exec %s "[EMAIL PROTECTED]"
This script should check to see if MACOSX_DEPLOYMENT_TARGET is
already set. If I have some reason to set
MACOSX_DEPLOYMENT_
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. This is definitely not true on Darwin, and
possibly other platforms. I have tested this on OpenBSD and Linux, and
the implementati
[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
On Jan 3, 2005, at 12:13 AM, Tim Peters wrote:
[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
[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
> Encryption/decryption support. Will most likely require a C extension since
> the algorithm relies on ints (or longs, don't remember) wrapping around when
> the value becomes too large.
You may want to do this in C for speed, but C-style int wrapping is
easily done by doing something like "x =
