How hard to allocate ALL Python data space (hence offset-based) in a memory mapped file image?

[Christian Tismer]

Manuel M. Garcia wrote:
> On 19 Dec 2002 06:51:08 GMT, bokr at oz.net (Bengt Richter) wrote:
> (edit)
> 
...
>>   python -k mydist.pyk
>>
>>which would magically continue after the sys.checkpoint call and mydist.pyk
>>would be the relevant mapped file ;-)
> 
> 
> Wow! This would be fantastic! It would end defininately all the
> complaints about Python's slowness at startup.
> 
> But I think Martin v. Löwis is correct.  CPython also keeps critical
> information on the C stack, so CPython data is mixed in with other
> data on the stack in an OS dependent way.
> 
> I don't know if Jython or Stackless would be able to do
> sys.checkpoint().  But it is more feasable for Jython or Stackless to
> do this than CPython.

This is a fact: There exists an extension to Stackless 1.0
that enables nearly exactly that: It pickles one thread,
which can be continued later, also on a different machine type.

Unfortunately, Stackless 1.0 no longer exists.

Fortunately, this feature will be re-invented in Stackless 3.0.

I-promise-to-show-it-on-PyCon -- ly y'rs - chris

-- 
Christian Tismer             :^)   <mailto:tismer at tismer.com>
Mission Impossible 5oftware  :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34  home +49 30 802 86 56  pager +49 173 24 18 776
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/