Perhaps? It seems this particular case could be solved by recognizing the newer naming convention for extension modules and not loading extensions that the current Python runtime wouldn't load (perhaps with a warning?).
Actually, the misbehavior is a little worse. My tree actually has _both_ CPython _and_ PyPy builds of these extension modules. pydoctor should pick up the CPython version when running on CPython and ignore the PyPy version.
Perhaps? It seems this particular case could be solved by recognizing the newer naming convention for extension modules and not loading extensions that the current Python runtime wouldn't load (perhaps with a warning?).
Actually, the misbehavior is a little worse. My tree actually has _both_ CPython _and_ PyPy builds of these extension modules. pydoctor should pick up the CPython version when running on CPython and ignore the PyPy version.
exarkun@ top:~/Projects/ Twisted/ trunk$ find -name '*.so' runner/ portmap. pypy-14. so runner/ portmap. so test/raiser. so python/ _initgroups. so python/ _initgroups. pypy-14. so python/ sendmsg. pypy-14. so python/ sendmsg. so internet/ _sigchld. pypy-14. so internet/ _sigchld. so top:~/Projects/ Twisted/ trunk$
./twisted/
./twisted/
./twisted/
./twisted/
./twisted/
./twisted/
./twisted/
./twisted/
./twisted/
exarkun@