Should be a thing of the past. In earlier years of computing, when 16bit operating systems were king, memory used to be addressed in segments/chunks of 64k (2**16). If you crossed one of those segments, you got a fault message. Python's memory manager shouldn't give you any problems like that! You might ask our friends in the C forum.
vegaseat
DaniWeb's Hypocrite
5,989 posts since Oct 2004
Reputation Points: 1,345
Solved Threads: 1,417
It's the error that gets thrown in C (and other languages with direct memory access) when you try to write to or read from a piece of memory you don't own.
As vega said, you should never see this error in Python, since Python doesn't allow you direct access to memory.
Out of curiousity, why do you ask?
Jeff
jrcagle
Practically a Master Poster
608 posts since Jul 2006
Reputation Points: 92
Solved Threads: 156
Scipy is written in C, must be that memory management is out of reach for Python to increase speed of certain functions within scipy.
vegaseat
DaniWeb's Hypocrite
5,989 posts since Oct 2004
Reputation Points: 1,345
Solved Threads: 1,417
Yeah, the seg fault is definitely not your fault. I recommend trying to find a work-around.
jrcagle
Practically a Master Poster
608 posts since Jul 2006
Reputation Points: 92
Solved Threads: 156