Closed shacker closed 8 years ago
Happy to take a pull request to fix this. :)
On Tue, 15 Dec 2015 at 01:54 Scot Hacker notifications@github.com wrote:
Under Django 1.9, on a fresh installation, running the initial migrations yields warnings:
Running migrations: Rendering model states... DONE Applying watson.0001_initial.../Users/me/.virtualenvs/portal/lib/python3.5/site-packages/django/core/management/base.py:577: RemovedInDjango110Warning: NoArgsCommand class is deprecated and will be removed in Django 1.10. Use BaseCommand instead, which takes no arguments by default. RemovedInDjango110Warning
12/14/2015 17:51:50 WARNING py.warnings:577 /Users/me/.virtualenvs/portal/lib/python3.5/site-packages/django/core/management/base.py:577: RemovedInDjango110Warning: NoArgsCommand class is deprecated and will be removed in Django 1.10. Use BaseCommand instead, which takes no arguments by default. RemovedInDjango110Warning
— Reply to this email directly or view it on GitHub https://github.com/etianen/django-watson/issues/147.
Would be happy to if I go forward with using watson on my current project. Right now I'm stuck on:
module 'watson' has no attribute 'register'
I may put more time into it later this week.
The latest release introduced some breaking changes.
https://github.com/etianen/django-watson/blob/master/CHANGELOG.markdown On Tue, 15 Dec 2015 at 18:31, Scot Hacker notifications@github.com wrote:
Would be happy to if I go forward with using watson on my current project. Right now I'm stuck on:
module 'watson' has no attribute 'register'
I may put more time into it later this week.
— Reply to this email directly or view it on GitHub https://github.com/etianen/django-watson/issues/147#issuecomment-164848431 .
Under Django 1.9, on a fresh installation, running the initial migrations yields warnings: