[Python-Dev] str object going in Py3K (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Thu Feb 16 04:00:16 CET 2006
- Previous message: [Python-Dev] str object going in Py3K
- Next message: [Python-Dev] str object going in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
M.-A. Lemburg wrote:
E.g. bytes.openfile(...) and unicode.openfile(...) (in 3.0 renamed to str.openfile())
This seems wrong to me, because it creates an unnecessary dependency of the bytes/str/unicode types on the file type. These types should remain strictly focused on being just containers for data.
-- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiam! | Christchurch, New Zealand | (I'm not a morning person.) | greg.ewing at canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-Dev] str object going in Py3K
- Next message: [Python-Dev] str object going in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]