Message264138
| Author |
gvanrossum |
| Recipients |
Ronan.Lamy, gvanrossum, larry, pitrou, pjenvey, serhiy.storchaka, vstinner |
| Date |
2016年04月25日.00:53:04 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJKgWAe6QHWPZG3dcJMWqo-W8iBOmmQ_pmBA7x8=qL7YwQ@mail.gmail.com> |
| In-reply-to |
<CAP7+vJJ=+kG=2L7egHjBa3We2cDByxk3Ss8iabQxVdj9-doWCA@mail.gmail.com> |
| Content |
Sigh, I was wrong, not only does mypy promote bytearray to bytes, it
actually depends on this in its own code. Not for filenames, but for a
regex match. It reads the source into a bytearray, and then passes that to
something that uses regex matches (which *do* support bytearrays, and
rightly so). If I remove the bytearray promotion I run into some type
errors, and if I fix those (without copying data) I run into more type
errors. I guess we could fix it by carefully marking up everything that
takes bytearrays in the stubs, but it's surely inconvenient. So maybe I'll
leave this in mypy for now. |
|