[Python-Dev] importlib is now bootstrapped (and what that means) (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Mon Apr 16 19:04:25 CEST 2012
- Previous message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Next message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I don't see how depending on Cython is better than depending on having an existing Python. If the only benefit is semi-readable code, surely we do have source code for the pre-frozen module, and it is just a matter of convincing hg that the bytecode is binary, not text?
Cython-generated C code would likely be more stable (and produce compiler errors if it gets stale), whereas importlib.h needs to be regenerated with byte code changes.
Having source code has the advantage that it becomes possible to single-step through the import process in C debugger. Single-stepping with pdb would, of course, be better than that, but I doubt it's feasible.
In addition, there might be a performance gain with Cython over ceval.
Regards, Martin
- Previous message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Next message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]