hearsaycorp / django-livefield Goto Github PK

I just upgraded to Django 1.9 and am getting this error below.

  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/django/db/models/manager.py", line 223, in all
      return self.get_queryset()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/livefield/managers.py", line 17, in get_queryset
      return qs.live()
AttributeError: 'InheritanceQuerySet' object has no attribute 'live'

Can you please release a version that is compatible with Django 2.1?

The GeoDjango extensions in livefield.gis need tests. It looks to me like we should be able to test all the functionality we've added on MySQL, Postgres, and SQLite.

@dyve, is this something you know how to tackle? I'll take a crack at it too, but I'm not sure how much progress I'll make.

how i can "delete" the childs of my parent object with this Livefieldmodel?

Could you please release a version that is compatible with Django 3.0?

django_livefield uses non-standard naming. There is still time to fix this (the app is young). I'd suggest this tree

• livefield
  • init.py
  • fields.py
  • managers.py
  • models.py
  • querysets.py
  • ...

This will help users to navigate the app easily, because the naming scheme is well known. I e-mailed about this a while back with @akshayjshah

We should add a test migration to make sure that the South integration works.

Sorry to keep piling on, @dyve - can you take this one on, too? I'd jump in, but I've never used South before.

I am using South 0.8.4 in a Django 1.6.10 project. I have the most recent version of django-livefield, with the LiveField added to one of my models. When I try to run a schemamigration I receive this error:

(sidekick)sidekick $ ./manage.py schemamigration agency --auto
 ! Cannot freeze field 'agency.agency.live'
 ! (this field has class livefield.fields.LiveField)

 ! South cannot introspect some fields; this is probably because they are custom
 ! fields. If they worked in 0.6 or below, this is because we have removed the
 ! models parser (it often broke things).
 ! To fix this, read http://south.aeracode.org/wiki/MyFieldsDontWork

I noticed the fields.py module has the following lines:

from south.modelsinspector import add_introspection_rules
add_introspection_rules([], ['^livefield.LiveField'])

yet the error is still occurring.

I'l submit a PR for Undelete views when the GeoDjango changes are in.

I haven't tested this, but in reviewing the code I am concerned with this line:

if lookup_type == 'exact' and not value:

In that block it says not to use value=False and to use value=None instead. However, it looks like passing in None will trigger that block, too:

$ ipython
In [1]: not None
Out[1]: True

In [2]: not False
Out[2]: True

Thoughts?

https://jazzband.co/

For the continued longevity and maintenance of django-livefield, perhaps submit it to the jazzband collective?

A PR has already been opened by a new contributor (yay!).

@rbm, would it be possible to put together a new release?

It'd be nice to have a pretty HTML site for documentation and examples.

I'd like to add this, already have it running in a live app. OK? Then I'll make pull request.

I'm just not sure how to add testing for these since I don't have a clue how to set up a spatial test db with the constructs this project is using. Is there anyone that can help out?

Can you please release a version that is compatible with Django 2.2?

I have already run tests locally for PostreSQL and SQLite and they passed.