I was thinking about this for a while. Owing to a lack of forking or START/STOP
signals, all process interchange in CPython requires serialisation, usually
pickling. But what if that could be done within the interpreter core instead of
by the script, creating a complete internal representation t
Damn Small Linux could work. If even that won't work, perhaps it's time to
scrap your old fossil for parts and buy a modern computer. Even a netbook would
probably be an improvement based on your situation.
--
http://mail.python.org/mailman/listinfo/python-list
Well for one, if you're writing with pywin32, you certainly don't need the
shbang line. #! /usr/bin/env is purely a POSIX thing.
--
http://mail.python.org/mailman/listinfo/python-list
Correct in that regard. In Python 3.x, strings are by default considered UTF-8.
Wheras ASCII isn't a problem because it's fixed-width, UTF-8 will give you a
different character depending on the last byte value. Therefore handling any
kind of data that is not UTF-8 will need you to open it with '
