Hi Samuele, you are not online, therefore using email. """ pedronis: stakkars_: btw my new hook allows to get back to a given module or function, or to skip things we know specialize fine """ I like the idea. Can't we go even a bit further? If we teach the specializer to not crash if something does not work out, but to add the problem blocks to a list, then we could have one report with all pending problems and work through this in a more general way. We also would get an estimate how much has still to be done. The process we are doing by hand (walking PDB stack, looking at the block etc.) can be either automated or deferred. Yes, deferring would be the easiest: The list of problem blocks should be pickleable for later analysis. The pickling might not be strong enough to re-run stuff at the moment, but for the debugging, it would surely be sufficient. cheers - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : 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 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/