[Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source (original) (raw)
Phillip J. Eby pje at telecommunity.com
Thu Sep 28 20:35:30 CEST 2006
- Previous message: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source
- Next message: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 11:25 AM 9/28/2006 -0700, Brett Cannon wrote:
I will think about it, but I am still trying to get the original question of how bad the C code is compared to rewriting import in Python from people. =)
I would say that the C code is delicate, not necessarily bad. In most ways, it's rather straightforward, it's actually the requirements that are complex. :)
A Python implementation, however, would be a good idea to have around for PyPy, Py3K, and other versions of Python, and as a refactoring basis for writing any new C code.
- Previous message: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source
- Next message: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]