This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients pitrou, r.david.murray, sable
Date 2011-02-17.16:45:51
SpamBayes Score 1.0214052e-14
Marked as misclassified No
Message-id <1297961145.3752.2.camel@localhost.localdomain>
In-reply-to <1297960441.62.0.491694004445.issue11212@psf.upfronthosting.co.za>
Content
> I think people may be more interested in setting permanently the
> maximum memory that can be allocated by python rather than using an
> environment variable that may be lost and which impacts all the
> applications.

Agreed, but it's impossible to standardize the configure script on a
"good enough" value. Some people might need 512MB, others 2GB...

> Another way to increase the memory available for an application is to
> use the ldedit command on the python executable:
> 
> ldedit -b maxdata:0x20000000 ./python
> 
> That may be easier than passing it directly to the linker.

Sounds better. That means that it can be decoupled from the build
process.
(although for a hypothetical buildbot, I think passing LDR_CNTRL would
be the most practical solution)
History
Date User Action Args
2011-02-17 16:45:52pitrousetrecipients: + pitrou, sable, r.david.murray
2011-02-17 16:45:51pitroulinkissue11212 messages
2011-02-17 16:45:51pitroucreate