On Fri, 9 Oct 2015 at 08:16 Robert Collins <robe...@robertcollins.net> wrote:
> But - ajax_select/__init__.py is going to be imported, and thats whats > erroring. I don't think that this is a 3.5 unit testing change - I > think its an error importing some bit of django. > Except there is no errors under Python2.7. If Python2.7 or Python3.4 loaded ajax_select/__init__.py I would expect to see exactly the same Django error. To test this out, I just put "raise RuntimeError()" into ajax_select/__init__.py I get the same results for Python2.7 and Python3.4, however Python3.5 generates the exception. So it does seem like it really is the case that Python3.5 now loads ajax_select/__init__.py when no tests exist, when this previously didn't happen. Bug #800137 is a complication. Am seriously thinking maybe we should backport the change (a very simple change) into our version of Django.
