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/2009-February/086265.html below:

[Python-Dev] IO implementation: in C and Python?

[Python-Dev] IO implementation: in C and Python? [Python-Dev] IO implementation: in C and Python?Antoine Pitrou solipsis at pitrou.net
Fri Feb 20 16:50:45 CET 2009
Guido van Rossum <guido <at> python.org> writes:
> 
> I worry that with your proposal people are once again going to import
> the pure Python version where they shouldn't. Maybe _pyio.py would
> work though?

I'm ok with _pyio.py.

> Hoping that modules won't evolve is futile. The concern for divergence
> is real. Unit-testing both with the same tests might be the solution.

Yes, the same tests should be applied to both (modulo the few ones that test for
implementation-specific behaviour, e.g. the max_buffer_size stuff).

Regards

Antoine.


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