Hi Stefan, > Ah, got it. This is just what Carl wrote in the initial bug report. The new > setup fails to provide a __getattr__ method and implements a > __getattribute__ method instead. But the problem is not only that the > introspection says it's not there, the problem is that the method really is > not there. So we break user code that tries to use __getattr__ as an > unbound method *and* the code generated by Cython for setting and > retrieving docstrings of this method, thus breaking the module > initialisation. So it's a double regression that is clearly user visible. > > Sounds like a release blocker to me. >
Robert and I were chatting about this earlier -- did the changes you pushed completely fix this problem, or just cover it up? We couldn't come up with a case that was still a problem off the cuff, but the commit message said something like "for now," which made us think that there might be more to the story. ;) -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
