Message 264136 - Python tracker

➜

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	gvanrossum
Recipients	Ronan.Lamy, gvanrossum, larry, pitrou, pjenvey, serhiy.storchaka, vstinner
Date	2016-04-25.00:31:17
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAP7+vJJ=+kG=2L7egHjBa3We2cDByxk3Ss8iabQxVdj9-doWCA@mail.gmail.com>
In-reply-to	<1461526243.35.0.305938533284.issue26800@psf.upfronthosting.co.za>

Content
OK, it isn't worth fighting for. I will update PEP 484. It seems mypy doesn't support the special treatment bytearray anyway. For posterity, the reason I thought that bytearray should be accepted is not that bytearray is better in any way, just that sometimes you might read a filename off a bytearray that you read off a file or a socket. But it's clearly not a strong use case (or we had gotten complaints long ago) so I'll let it go. Sorry!! Thanks for the feedback.

OK, it isn't worth fighting for. I will update PEP 484. It seems mypy
doesn't support the special treatment bytearray anyway.

For posterity, the reason I thought that bytearray should be accepted is
not that bytearray is better in any way, just that sometimes you might read
a filename off a bytearray that you read off a file or a socket. But it's
clearly not a strong use case (or we had gotten complaints long ago) so
I'll let it go. Sorry!! Thanks for the feedback.

History
Date	User	Action	Args
2016-04-25 00:31:18	gvanrossum	set	recipients: + gvanrossum, pitrou, vstinner, larry, pjenvey, serhiy.storchaka, Ronan.Lamy
2016-04-25 00:31:18	gvanrossum	link	issue26800 messages
2016-04-25 00:31:17	gvanrossum	create