[Python-Dev] s/bytes/octet/ [Was:Re: bytes.from_hex() [Was: PEP 332 revival in coordination with pep 349?]]
Delaney, Timothy (Tim)
tdelaney at avaya.com
Tue Feb 21 23:23:39 CET 2006
More information about the Python-Dev mailing list
Tue Feb 21 23:23:39 CET 2006
- Previous message: [Python-Dev] Two patches
- Next message: [Python-Dev] s/bytes/octet/ [Was:Re: bytes.from_hex() [Was: PEP332 revival in coordination with pep 349?]]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greg Ewing wrote: > I don't quite see the point here. Inside a bytes object, > they would be stored 1 byte per byte. Nobody is suggesting > that they would take up more than that just because > a_bytes_object[i] happens to return an int. Speaking of which, I suspect it'll be a lot more common to need integer objects in the full range [0, 255] than it is now. Perhaps we should extend the pre-allocated integer objects to cover the full byte range. Tim Delaney
- Previous message: [Python-Dev] Two patches
- Next message: [Python-Dev] s/bytes/octet/ [Was:Re: bytes.from_hex() [Was: PEP332 revival in coordination with pep 349?]]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list