Skip to content

Switch to use non-forked version of django-comments-xtd - #1120

Merged
berkerpeksag merged 1 commit into
python:masterfrom
berkerpeksag:upgrade-xtd
Aug 9, 2017
Merged

berkerpeksag merged 1 commit into
python:masterfrom
berkerpeksag:upgrade-xtd

Conversation

@berkerpeksag

Copy link
Copy Markdown
Member

The version we've been using doesn't support new migrations
so we can't write a data migration without proper
migration files.

The built-in comments application also doesn't have migrations
so we had to switch to 'django_comments'.

We have to use a forked version because of the following line
in setup.py:

install_requires=['Django>=1.6']

This would install the latest stable version of Django which
would break our application.

The version we've been using doesn't support new migrations
so we can't write a data migration without proper
migration files.

The built-in comments application also doesn't have migrations
so we had to switch to 'django_comments'.

We have to use a forked version because of the following line
in setup.py:

    install_requires=['Django>=1.6']

This would install the latest stable version of Django which
would break our application.
@berkerpeksag
berkerpeksag merged commit 3bd1ad5 into python:master Aug 9, 2017
@berkerpeksag
berkerpeksag deleted the upgrade-xtd branch August 9, 2017 20:44
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

Successfully merging this pull request may close these issues.

1 participant