A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-June/135086.html below:

[Python-Dev] Why does _pyio.*.readinto have to work with 'b' arrays?

[Python-Dev] Why does _pyio.*.readinto have to work with 'b' arrays? [Python-Dev] Why does _pyio.*.readinto have to work with 'b' arrays?Benjamin Peterson benjamin at python.org
Sun Jun 15 02:41:44 CEST 2014
On Sat, Jun 14, 2014, at 15:39, Nikolaus Rath wrote:
> It seems to me that a much cleaner solution would be to simply declare
> _pyio's readinto to only work with bytearrays, and to explicitly raise a
> (more helpful) TypeError if anything else is passed in.

That seems reasonable. I don't think _pyio's behavior is terribly
important compared to the C _io module.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4