[summerofcode] SpeedUpInterpreterStartup - IDEAS

[Misto .]

> Since I tossed up that idea I should probably reply to you.  =)

Thanks!
> 
> Sounds like a plan.  Easy way to test startup time is to execute Python under
> 'time' with nothing but 'pass' to be executed; ``time python -c "pass"``.

Ok that is the basic test.
I am tryng to obtain a precise profile of the time that each component
takes in being loaded.

Seems that this guy have something usefull

http://www.nickbastin.com/archives/000160.php

I'll try to contact him...

> That is probably a waste of time.  Psyco only tweaks the eval loop, nothing
> more.  And because Psyco is x86-only it won't work for Python itself since it
> needs to work with any C compiler with POSIX libraries.
Ah ok. Time gained.

> In other words any changes need to work with *all* platforms Python supports.
Ack!

> Martin v. Löwis and Nick Bastin worked on this at PyCon 2004.  They discovered
> that site.py was very costly to import (partially because of the distutils
> import).  After that some other modules that were imported were costly (I think
> 'warnings' was expensive to import since it is pure Python and uses the 're'
> module heavily).
Thanks for this!

> Any good ideas or material concerning the topic is welcome.

I have seen the patch that nick bastin has proposed.

https://sourceforge.net/tracker/?func=detail&atid=305470&aid=920509&group_id=5470

I'll try to hack a bit with this.
 
> Don't get to heavy into this, Misto.  
Don't worry. 
I think that speeding up Python is fundamental to improve the use of
this language.
I think that with a faster startup many little applications "type and
run" will be more
usefull.

> I don't want you to sent in a proposal
> and get rejected after a ton of work.  Unless of course you enjoy it!  If so,
> then go wild!  =)

I'll try to speed up the startup.
If the google team will accept me I will dedicate a good amount of my
summer time to accomplish the project.
Otherwise I'll spend more time in my italian summer house. :D

Misto