use timezone.now() instead of datetime.today() to determine time #5
Conversation
Django 1.4 requires datetime instances to be time zone aware by default.
|
btw, the API seems to be outdated. You guys switched to a very different model, but the docs are still the same. Is there anywhere I can see how to do the stuyff that is being done in the API? |
|
Not at the moment…sorry. The API docs are indeed outdated and they don't reflect the new model that is being used. You can look at your console to see which http requests are being executed by django-locking. That will give you a sense as to how the ajax calls are communicating with the views. From that point, you can deduce the api calls that are needed for your purpose. We'll gladly accept a patch to get those docs updated once you get that figured out. Thanks! RobCombs | Sr. Software Engineer, technology | CMGdigital From: johanneswilm <[email protected]mailto:[email protected]> btw, the API seems to be outdated. You guys switched to a very different model, but the docs are still the same. Is there anywhere I can see how to do the stuyff that is being done in the API? — |
|
I believe this last addition should make ti compatible with django 1.3 |
|
btw, I gave up on django-locking and moved on to django-simple-lock. They just updated their documentation. |
|
Sounds good. Thanks for the update! From: johanneswilm <[email protected]mailto:[email protected]> btw, I gave up on django-locking and moved on to django-simple-lock. They just updated their documentation. — |
|
Hello, I got an error that I think is related to this issue. And just git clone the repository. Using Django 2.4 and Python 2.7. can't subtract offset-naive and offset-aware datetimes django_locking-0.3.2-py2.7.egg/locking/models.py in is_locked, line 88 Thank you Louis |
Django 1.4 requires datetime instances to be time zone aware by default.