Re: [Python-Dev] [ANN] VPython 0.1
"Phillip J. Eby" <[EMAIL PROTECTED]> writes: > At 10:47 AM 10/24/2008 +0200, J. Sievers wrote: >> - Right now, CPython's bytecode is translated to direct threaded code >> lazily (when a code object is first evaluated). This would have to >> be merged into compile.c in some way plus some assorted minor changes. > > Don't you mean codeobject.c? I don't see how the compiler relates, as > Python programs can generate or transform bytecode. (For example, > Zope's Python sandboxing works that way.) > Also good :). (I was thinking about the superinstruction selection code which should perhaps go into optimize_code() since it's a kind of peephole optimization. The bytecodes->addresses part might even stay in ceval.c I guess). -jakob ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [ANN] VPython 0.1
Stefan Behnel wrote: That's obviously a problem, but it only answers the second question, not the first one. [does using a generator for the VM make life easier for the Stackless Python developers in any way?] The Stackless Python developers themselves would have to answer that one, but my guess is that it would help about the same amount as it would help non-Stackless Python, i.e. there's not much about stacklessness per se that makes it particularly beneficial to have a generated VM. -- Greg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] is the 'path' argument to an importer's find_module() just a hint?
I just discovered frozen packages set their __path__ simply to their name and not to a list as expected (http://bugs.python.org/issue4211). This made me think about the 'path' argument to find_module() and whether it can be treated as simply a hint or should always be seriously looked at. Take frozen modules, for instance. If the 'path' argument is meant to always be considered then if a frozen module is within a package a check should be done to make sure that the parent package is in 'path' somewhere. But if it is simply a hint, then 'path' should be ignored and whether the module can be found should depend fully on imp.is_frozen(). So, what do people think? Should 'path' for find_module() always be taken into consideration, or only when it happens to be convenient? -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
