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/086282.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?Greg Ewing greg.ewing at canterbury.ac.nz
Fri Feb 20 22:15:17 CET 2009
Steven D'Aprano wrote:

> Currently, if I want to verify that (say) cFoo and Foo do the same 
> thing, or compare their speed, it's easy because I can import the 
> modules separately.

Also, won't foo.py be wasting time in most cases by
defining python versions that get overwritten?

Instead of defining things directly in foo.py, maybe it
should do

   try:
     from cFoo import *
   except ImportError:
     from pyFoo import *

Then the fast path will be taken if cFoo is available,
and you can directly import cFoo or pyFoo if you want.

-- 
Greg
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