On Sep 17, 2008, at 12:45 PM, Martin v. Löwis wrote: >> I'll take this up with FreeBSD folk, but I'm open to ideas as to how >> best to deal with the problem in the context of the test suite >> pending >> resolution by FreeBSD. > > Not sure what the test purpose is: if it is to test that you get a > MemoryError in cases where you ask for more than Python could > represent, > and the test errs on system where the requested size is actually > representable, the solution then is to fix the test case. > > If the test purpose is to trigger a memory error for cases when the > system runs out of memory, the test case should set a ulimit to less > than the physical memory. > > It might be useful to have an interpreter-maintained limit on the > amount > of memory Python can consume, but such a feature is clearly out of > scope > for the current state of the code. There is an option at least on linux to hack using ld preload to use another memory manager that respond the way needed... at least that was what I was told today at lunch. (if ulimit is not enough for any reason). -- Leonardo Santagada santagada at gmail.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4