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 eric.araujo
Recipients Trundle, benjamin.peterson, brett.cannon, eric.araujo, eric.snow, ncoghlan, vstinner
Date 2012-02-23.00:35:05
SpamBayes Score 5.85708e-11
Marked as misclassified No
Message-id <>
> I also think that [there] is still too much C code as it makes the whole thing somewhat brittle
> to any refactoring of importlib. I am seriously thinking of tossing the C code I have written and
> writing in C only the bare minimum needed to get to the sys.modules check, and otherwise punting
> to importlib for everything else in a single call or two.

A few thoughts from my outsider viewpoint:

1) I think the point of importlib is to have maintainable code (i.e. the anti-import.c <wink>), so writing only the minimum code in C makes sense.

2) Speed is a concern, especially with sysconfig in 3.3 slowing startup, but a secondary concern.

3) Maybe some parts can be written in C later, after profiling, and then override Python functions (à la “from _heapq import *”, if that’s possible at all for importlib).

4) When is PyPy going to be the reference implementation again?  Then we’ll have no speed issues—ha ha only serious.

5) importlib rocks hard.
Date User Action Args
2012-02-23 00:35:07eric.araujosetrecipients: + eric.araujo, brett.cannon, ncoghlan, vstinner, benjamin.peterson, Trundle, eric.snow
2012-02-23 00:35:07eric.araujosetmessageid: <>
2012-02-23 00:35:05eric.araujolinkissue2377 messages
2012-02-23 00:35:05eric.araujocreate