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.

Sign up for GitHub

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

Jump to bottom

Django 2 plans #84

Closed
crccheck opened this issue Oct 17, 2017 · 2 comments
Closed

Django 2 plans #84

crccheck opened this issue Oct 17, 2017 · 2 comments
Labels
help wanted

Comments

@crccheck
Copy link
Owner

With Django 2 on the horizon, the plan is to release what I got as v1, trying to get as many of these naming things issues #44 out of the way as possible.

django-object-actions will have a v2 release for Django 2 with no backwards compatibility. The v1 release will get basic patches, time permitting
@danmoz
Copy link
Contributor

danmoz commented Feb 27, 2018

I was just wondering, now that Django 2.0 is officially released, are there any plans for a new release?

Would you accept a Django 2.0 PR that doesn't address the issues in #44?

@crccheck
Copy link
Owner Author

oof, yeah, sounds good

@danmoz danmoz mentioned this issue Mar 3, 2018
Merged
crccheck pushed a commit that referenced this issue Mar 9, 2018
@danmoz @crccheck
Add support for Django 2.0 (#85)
430be02 
Adding support for Django 2.0+, and removing support for Django versions up to 1.8, the oldest supported LTS release. This allows us to replace the now deprecated django-extensions UUIDField with the Django native version, and drop a couple of other hacks. Resolves #84
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crccheck @danmoz