Hallöchen!
Tim Graham writes:
> Could you try Python 3.4.x?
The problem does not exist with Python 3.4.3. (Ubuntu 14.04)
> I ran into some issues with Django's own test suite [0] due to
> some import changes in Python 3.5 [1].
If I look at Python 3.5's release notes, the following is
suspicious:
Found packages are now checked for load_tests regardless of
whether their path matches pattern, because it is impossible for
a package name to match the default pattern.
I understand this this way: The pattern still works for .py files
but not for packages (__init__.py files). And since my models'
__init__.py says
from .physical_processes import *
and the app is not yet set up, this breaks.
Question is: Is is bad style to have a models *package* which
collects alls models in its __init__.py, or has Django to be adapted
to Python's new behaviour?
Tschö,
Torsten.
--
Torsten Bronger Jabber ID: [email protected]
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/87potbc87j.fsf%40physik.rwth-aachen.de.
For more options, visit https://groups.google.com/d/optout.
