Skip to content
This repository was archived by the owner on Jun 20, 2018. It is now read-only.

Django 1.8 support (WITH admin module)#22

Open
bijanvakili wants to merge 1 commit into
disqus:masterfrom
bijanvakili:master
Open

Django 1.8 support (WITH admin module)#22
bijanvakili wants to merge 1 commit into
disqus:masterfrom
bijanvakili:master

Conversation

@bijanvakili
Copy link
Copy Markdown

This is a fix for Django 1.8 so that the AdminSite can work if the 'app_name' argument is no longer available.

This is also backwards compatible with Django <= 1.7

@bijanvakili bijanvakili changed the title Django 1.8 support (without admin module) Django 1.8 support (WITH admin module) Jun 9, 2015
@craiglabenz
Copy link
Copy Markdown

Any reason this is yet unmerged?

@mattrobenolt
Copy link
Copy Markdown
Collaborator

Because we have no way to validate this. We don't run Django 1.8, so getting some to review and test this is a bit cumbersome. Sorry. :(

@craiglabenz
Copy link
Copy Markdown

Any way outsiders can help?

@Fluxx
Copy link
Copy Markdown

Fluxx commented Jun 23, 2015

Any way outsiders can help?

Yes, if someone outside is willing to get a build matrix setup to test different versions of Django (and python) and add that, we'll be likely to accept it. At present Nexus has very little to no active usage inside Disqus so we don't have a ton of organization momentum to help maintain it. That's obviously not great news to hear but it's the reality of the situation.

@craiglabenz
Copy link
Copy Markdown

Fair enough. For now I've just forked, accepted that PR myself, and am moving forward. Appreciate that the lib even exists at all :)

@adamchainz
Copy link
Copy Markdown
Contributor

#24 adds this plus tests in a build matrix with tox 😄

@giftig
Copy link
Copy Markdown

giftig commented Oct 1, 2015

Thanks @craiglabenz, I just ran into this issue while upgrading my django version to 1.8; I'll probably use your fork 👍

@giftig
Copy link
Copy Markdown

giftig commented Oct 1, 2015

Actually from what I can see, nexus 0.3.1 works fine with django 1.8; my problem now is with the gargoyle module. Is this pull request still needed? Upgrading from 0.3.0 to 0.3.1 of nexus fixed the issue described above for me.

@sssbox
Copy link
Copy Markdown

sssbox commented Oct 1, 2015

We ran into a few other issues with nexus and django 1.8. This is how we got it to work (including some changes from the pull requests in this conversation): master...brilliant-org:master

Also, gargoyle needed a few small changes: disqus/gargoyle@master...brilliant-org:master

@adamchainz
Copy link
Copy Markdown
Contributor

Hey guys, you can install the YPlan branch which has tests and throws no warnings for us on Django 1.8 https://github.com/yplan/nexus/tree/yplan_django18 . We also have a gargoyle branch https://github.com/yplan/gargoyle/tree/yplan_django18

@craiglabenz
Copy link
Copy Markdown

Very cool @adamchainz -- great work!

@adamchainz
Copy link
Copy Markdown
Contributor

You can now pip install nexus-yplan and gargoyle-yplan.

@giftig
Copy link
Copy Markdown

giftig commented Dec 9, 2015

Cool, I'll give them a go; thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants