Hi Armin,
Uh, that's strange. The docstrings in interpreter/module.py say
specifically the opposite. But the truth looks a bit more complicated
indeed, e.g. it depends if getbuiltinmodule('cppyy') was already
called during translation or not...
yes, that is called, and it is being called by having applevel defs, b/c
pythonify.py does an "import cppyy" at the module level.
So, the solution then, is to not do that. :) I now have a _init_pythonify
applevel def that does all setup that touches cppyy. That is then called
in startup() as you told me to do. All other references to cppyy have an
import just before them (i.e. inside the function) and the module-level
one has been removed. Looks a bit strange, but does work as I want it: now
nothing runs on ./pypy-c startup, and gbl & friends are build on import.
Thanks!
Best regards,
Wim
--
wlavrij...@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
