On Thu, Jun 24, 2010 at 11:53, Éric Araujo <merwok at netwok.org> wrote: > Le 24/06/2010 19:48, Brett Cannon a écrit : >> P.S.: I wish we could drop use of the 'module.so' variant at the same >> time, for consistency sake and to cut out a stat call, but I know that >> is asking too much. > > At least, looking for spam/__init__module.so could be avoided. It seems > to me that the package definition does not allow that. I thought no one had bothered to change import.c to allow for extension modules to act as a package's __init__? As for not being allowed, I don't agree with that assessment. If you treat a package's __init__ module as simply that, a module that would be named __init__ when imported, then __init__module.c would be valid (and that's what importlib does). > The tradeoff > would be code complication for one less stat call. Worth a bug report? Nah.
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