This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mgiuca
Recipients georg.brandl, loewis, mgiuca
Date 2008-08-16.09:59:15
SpamBayes Score 4.14002e-10
Marked as misclassified No
Message-id <1218880756.53.0.654958057792.issue3565@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm not a native speaker (of English), but my understanding is that the
> noun "string", in itself, can very well be used to describe this type:
> the result is a "byte string", as opposed to a "character string".
> Merriam-Webster's seems to agree; meaning 5b(2) is "a sequence of like
> items (as bits, characters, or words)"

Ah yes, that's quite right (and computer science literature will
strongly support that claim as well).

However the word "string", unqualified, and in Python 3.0 terminology
(as described in PEP 358) now refers only to the "str" type (formerly
known as "unicode"), so it is very confusing to have a method "tostring"
which returns a bytes object.

For array to become a good Py3k citizen, I'd strongly argue that
tostring/fromstring should be renamed to tobytes/frombytes. I'm
currently writing a patch for that - it looks like there's very minimal
damage.

However as a separate issue, I think the documentation update should be
approved first.
History
Date User Action Args
2008-08-16 09:59:16mgiucasetrecipients: + mgiuca, loewis, georg.brandl
2008-08-16 09:59:16mgiucasetmessageid: <1218880756.53.0.654958057792.issue3565@psf.upfronthosting.co.za>
2008-08-16 09:59:15mgiucalinkissue3565 messages
2008-08-16 09:59:15mgiucacreate