Re: undeclared variable appearing in django/db/models/__init__.py

2016-10-07 Thread Tim Graham
Thanks for the pointer! I think Django is misbehaving by importing "from django.db.models import *" in "django/contrib/gis/db/models/__init__.py" while django.db.models doesn't declare an __all__, so the "functions" submodule can be imported there which obscures the version at

Re: undeclared variable appearing in django/db/models/__init__.py

2016-10-07 Thread Peter Inglesby
Hi Tim, Disappointingly, I don't think Django's doing anything off the wall here! When you import a package's submodule, the name of that submodule is added to the package's namespace. This is what allows you to put `import p.m`, and to then to use `p.m` in your code -- module m is added to

undeclared variable appearing in django/db/models/__init__.py

2016-10-06 Thread Tim Graham
I'm seeing an issue while running the Django test suite that I can't explain. If you add print(functions) before from django.db.models.manager import Manager in https://github.com/django/django/blob/master/django/db/models/__init__.py#L15, it gives name 'functions' is not defined as I would