Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jacob Kaplan-Moss: deprecate django.contrib.comments #42

Closed
emacsway opened this issue Mar 8, 2013 · 3 comments
Closed

Jacob Kaplan-Moss: deprecate django.contrib.comments #42

emacsway opened this issue Mar 8, 2013 · 3 comments

Comments

@emacsway
Copy link

emacsway commented Mar 8, 2013

Jacob Kaplan-Moss: "This one's simple: I'd like to deprecate django.contrib.comments,
scheduling it to be removed in a couple of releases." http://groups.google.com/group/django-developers/msg/8cb9cdb049fe721d

"If someone volunteers to maintain it as an external project I'll move
the code to a new repo and direct people there in the docs. If nobody
volunteers, then it'll go to the great /dev/null in the sky."

@vdboor
Copy link
Collaborator

vdboor commented Mar 9, 2013

Thx for letting us know, we'll look into it! :)

@vdboor
Copy link
Collaborator

vdboor commented May 28, 2013

For everyones info, Django's contrib.comments module has moved to https://github.com/django/django-contrib-comments I've love to see this module being aligned with that; we'll monitor the repo and transition to it when it's time.

@vdboor
Copy link
Collaborator

vdboor commented Apr 14, 2015

This is now supported in django-threadedcomments 1.0b1 !
When django_comments is added to INSTALLED_APPS, it will be picked up by default.
For Django 1.7 and 1.8 this is required, as the migrations depend on it.

@vdboor vdboor closed this as completed Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants