Message104579
> But maybe this is not so important, as these are programming errors
> anyway.
Agreed :)
> One thing I'm still wondering : why couldn't we obtain these C
> extension by cythonizing _pyio ? Are there features that cython lacks,
> or optimization considerations I'm not aware of ? Cython-generated
> extensions seem soooo easier to maintain...
Several reasons:
- we don't want to depend on an external tool such as cython; the interpreter and its most critical modules just need a C compiler and a reasonably standard C library
- the language cython implements is not Python: it is both a superset and (more annoyingly) a subset of Python
- cython will not allow us, I think, to do as many optimizations as we do in the C version of the io library; the algorithms used are not the same as in the Python version, since raw C allows some much more efficient constructs (especially for handling memory buffers) |
|
Date |
User |
Action |
Args |
2010-04-29 20:16:16 | pitrou | set | recipients:
+ pitrou, amaury.forgeotdarc, vstinner, giampaolo.rodola, ajaksu2, pakal |
2010-04-29 20:16:16 | pitrou | set | messageid: <1272572176.27.0.4493226767.issue7865@psf.upfronthosting.co.za> |
2010-04-29 20:16:15 | pitrou | link | issue7865 messages |
2010-04-29 20:16:14 | pitrou | create | |
|