Django 1.8 support

[nemesifier]

• fix crappy GEODJANGO_INSTALLED redundant flag
• run tests with django 1.8 and see what breaks
• find solution for transaction.is_managed
• cannot import django.contrib.gis.db.models.sql.query
• ensure HStoreGeoQuerySet works
• InterfaceError: connection already closed
• test_reload_schema fails

Work in progress..

[coveralls]

Coverage increased (+0.62%) to 92.63% when pulling 5d6ab87 on django-1.8 into a78545f on master.

[coveralls]

Coverage increased (+0.62%) to 92.63% when pulling 5d6ab87 on django-1.8 into a78545f on master.

[coveralls]

Coverage increased (+0.62%) to 92.63% when pulling 5d6ab87 on django-1.8 into a78545f on master.

[coveralls]

Coverage increased (+0.62%) to 92.63% when pulling 5d6ab87 on django-1.8 into a78545f on master.

[landscape-bot]

Repository health increased by 0.48% when pulling 5d6ab87 on django-1.8 into a78545f on master.

• 2 new problems were found (including 1 error and 1 code smell).
• 5 problems were fixed (including 1 error and 4 code smells).

[landscape-bot]

Code quality remained the same when pulling 5d6ab87 on djangonauts:django-1.8 into 1beec30 on djangonauts:master.

[landscape-bot]

Repository health decreased by 1% when pulling 5d6ab87 on django-1.8 into 0ac2b02 on master.

• 3 new problems were found (including 1 error and 2 code smells).
• No problems were fixed.

[landscape-bot]

Code quality remained the same when pulling 6ebff43 on djangonauts:django-1.8 into 8bf5a1b on djangonauts:master.

[coveralls]

Coverage decreased (-0.76%) to 91.98% when pulling 6ebff43 on django-1.8 into 8bf5a1b on master.

[coveralls]

Coverage decreased (-0.76%) to 91.98% when pulling 6ebff43 on django-1.8 into 8bf5a1b on master.

[xeor]

Is this coming out in django-hstore v1.4? Any ETA?

[nemesifier]

i'm working on it in my free time, I can't provide an ETA.

[xeor]

As a side-note.. Can you please add a paypal donate button or something on your site? I totally understand that you are doing this in your free time. Just wanted to buy you a beer :) Appreciate your work!

[nemesifier]

very kind of you @xeor, but haven't felt the need of donations yet. I might consider this in the future.
Many people have contributed to this library, I think they'll come back to contribute as soon as they'll need this library to work with their django 1.8 project, unless I finish earlier.

[aidanlister]

So now that there's a HStoreField, will django-hstore wrap that to provide the extra functionality like schema?
https://docs.djangoproject.com/en/1.8/ref/contrib/postgres/fields/#hstorefield

[nemesifier]

@aidanlister: probably in a later release, I've analyzed the amount of work to do this and it will take quite few weeks of work. A gradual implementation sounds more realistic.

[bijanvakili]

@nemesisdesign +1

The work you've done with schema and virtual fields is awesome. Since these don't come with django.contrib.postgres, we'd rather stick with django-hstore. If you need help with incrementally supporting Django 1.8, please feel free to reach out.

[aidanlister]

Just as a note for 1.8ers, you can now enable hstore in a migration:

from django.contrib.postgres.operations import HStoreExtension

class Migration(migrations.Migration):
...

operations = [
    HStoreExtension(),
    ...
]

[nemesifier]

@bijanvakili yes help is appreciated as right now i cannot work on this, if anyone has a bit of time can just proceed on this branch, i'll give him/her write access to push to the 1.8 branch

[aidanlister]

I'm testing the new 1.8 functionality in our staging environments now, soon to move into production which is a little scary.

The only incompatibility we've noticed at the initialisation level is having HStoreExtension in your migrations doesn't help you, because register_hstore_handler (https://github.com/djangonauts/django-hstore/blob/master/django_hstore/apps.py#L42) runs first and crashes out.

You'll need to set up hstore before the connection is established if you want to keep using django-hstore.

@nemesisdesign I might be able to spare a developer for a few days to work on 1.8 compatibility, there does seem to be a 1.8 blocker which is that ConcreteField issue I posted.

[landscape-bot]

Repository health decreased by 0.03% when pulling 4b60bd5 on django-1.8 into 641c2e0 on master.

• 3 new problems were found (including 2 errors and 1 code smell).
• 3 problems were fixed (including 2 errors and 1 code smell).

[nemesifier]

After fd33e31 and 4b60bd5 there are a few more issues we can work on.

[coveralls]

Coverage decreased (-0.94%) to 91.8% when pulling 4b60bd5 on django-1.8 into 641c2e0 on master.

[aidanlister]

Traceback:
File "/app/.heroku/python/lib/python3.4/site-packages/django/core/handlers/base.py" in get_response
  132.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/contrib/admin/options.py" in wrapper
  616.                 return self.admin_site.admin_view(view)(*args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/utils/decorators.py" in _wrapped_view
  110.                     response = view_func(request, *args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
  57.         response = view_func(request, *args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/contrib/admin/sites.py" in inner
  233.             return view(request, *args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/utils/decorators.py" in _wrapper
  34.             return bound_func(*args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/utils/decorators.py" in _wrapped_view
  110.                     response = view_func(request, *args, **kwargs)
File "/app/.heroku/python/lib/python3.4/site-packages/django/utils/decorators.py" in bound_func
  30.                 return func.__get__(self, type(self))(*args2, **kwargs2)
File "/app/.heroku/python/lib/python3.4/site-packages/django/contrib/admin/options.py" in changelist_view
  1655.             selection_note=_('0 of %(cnt)s selected') % {'cnt': len(cl.result_list)},
File "/app/.heroku/python/lib/python3.4/site-packages/django/db/models/query.py" in __len__
  144.         self._fetch_all()
File "/app/.heroku/python/lib/python3.4/site-packages/django/db/models/query.py" in _fetch_all
  965.             self._result_cache = list(self.iterator())
File "/app/.heroku/python/lib/python3.4/site-packages/django/db/models/query.py" in iterator
  255.             obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
File "/app/.heroku/python/lib/python3.4/site-packages/django/db/models/base.py" in from_db
  489.             new = cls(*values)
File "/app/.heroku/python/lib/python3.4/site-packages/django/db/models/base.py" in __init__
  482.         signals.post_init.send(sender=self.__class__, instance=self)
File "/app/.heroku/python/lib/python3.4/site-packages/django/dispatch/dispatcher.py" in send
  201.             response = receiver(signal=self, sender=sender, **named)
File "/app/abas/apps/siteconfig/signals/handlers.py" in update_schema
  27.         field.reload_schema(schema)
File "/app/.heroku/python/lib/python3.4/site-packages/django_hstore/fields.py" in reload_schema
  185.         self._remove_hstore_virtual_fields()
File "/app/.heroku/python/lib/python3.4/site-packages/django_hstore/fields.py" in _remove_hstore_virtual_fields
  209.                 getattr(cls._meta, meta_fields).remove(field)
File "/app/.heroku/python/lib/python3.4/site-packages/django/utils/datastructures.py" in complain
  500.             raise AttributeError(self.warning)

Exception Type: AttributeError at /admin/properties/property/
Exception Value: The return type of 'fields' should never be mutated. If you want to manipulate this list for your own use, make a copy first.

Because we're dealing with the new _meta API, removing fields is a no-no. reload_schema removes all the hstore fields and re-adds them which isn't allowed.

[aidanlister]

Alright I think this commit fixes the above: https://github.com/ABASystems/django-hstore/commit/4f295149016e80423e100bba31fc748b49cff9ac

[landscape-bot]

Repository health decreased by 0.03% when pulling 3844307 on django-1.8 into b31f891 on master.

• 3 new problems were found (including 2 errors and 1 code smell).
• 3 problems were fixed (including 2 errors and 1 code smell).

[coveralls]

Coverage decreased (-0.94%) to 91.8% when pulling 3844307 on django-1.8 into b31f891 on master.

[coveralls]

Coverage decreased (-0.9%) to 91.802% when pulling 3844307 on django-1.8 into b31f891 on master.

[nemesifier]

@aidanlister thx for https://github.com/ABASystems/django-hstore/commit/4f295149016e80423e100bba31fc748b49cff9ac

regarding the connection, django's HStoreField is very similar to django-hstore, see this comment: #76 (comment)

I just pushed some more commits, let's wait and see.

[landscape-bot]

Repository health decreased by 0.10% when pulling 8af4c0b on django-1.8 into b31f891 on master.

• 9 new problems were found (including 3 errors and 6 code smells).
• 7 problems were fixed (including 3 errors and 4 code smells).

[landscape-bot]

Repository health decreased by 0.10% when pulling 8af4c0b on django-1.8 into b31f891 on master.

• 9 new problems were found (including 3 errors and 6 code smells).
• 7 problems were fixed (including 3 errors and 4 code smells).

[coveralls]

Coverage decreased (-0.45%) to 92.29% when pulling 8af4c0b on django-1.8 into b31f891 on master.

[landscape-bot]

Repository health decreased by 0.02% when pulling f9462a0 on django-1.8 into b31f891 on master.

• 10 new problems were found (including 3 errors and 7 code smells).
• 7 problems were fixed (including 3 errors and 4 code smells).

[coveralls]

Coverage increased (+0.54%) to 93.28% when pulling f9462a0 on django-1.8 into b31f891 on master.

[coveralls]

Coverage increased (+0.54%) to 93.28% when pulling f9462a0 on django-1.8 into b31f891 on master.

[nemesifier]

Now please help us testing it in the real world!

[aidanlister]

Is there any reason you're checking fields and other_fields rather than virtual_fields?

[nemesifier]

@aidanlister could you be more specific?

[aidanlister]

You're iterating fields, local_fields and virtual_fields ... I think you can just iterate virtual_fields: https://github.com/djangonauts/django-hstore/blob/master/django_hstore/fields.py#L215

See https://github.com/ABASystems/django-hstore/blob/django-1.8/django_hstore/fields.py#L204

[nemesifier]

It's a bit more complex than that. simple virtual fields did not work in the admin by default because inconsistencies between django models and django modeladmin, so I had to pretend virtual fields are also real fields, that's why i was iterating also on other lists.