Message77910
Good luck with that. Most people who get bright ideas such as "gee,
maybe I'll write my own version of X" where "X" is some part of the
standard C library pertaining to I/O, end up fighting a losing battle.
Of course, I'd love to be proven wrong, but I don't think I will in this
case.
As for cranking data, that does not necessarily imply heavy-duty CPU
processing. Someone might be reading large datafiles simply to perform
some kind of data extraction, filtering, minor translation, or other
operation that is easily carried out in Python, but where the programs
are still I/O bound. For example, the kinds of processing one might
otherwise do using awk, sed, perl, etc. |
|
Date |
User |
Action |
Args |
2008-12-16 14:07:39 | beazley | set | recipients:
+ beazley, georg.brandl, rhettinger, amaury.forgeotdarc, pitrou, giampaolo.rodola, christian.heimes, donmez, wplappert |
2008-12-16 14:07:39 | beazley | set | messageid: <1229436459.56.0.451809761495.issue4561@psf.upfronthosting.co.za> |
2008-12-16 14:07:39 | beazley | link | issue4561 messages |
2008-12-16 14:07:38 | beazley | create | |
|