-
Notifications
You must be signed in to change notification settings - Fork 31
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
Django 2.0 compatibility #22
Comments
The import should be You can use It's in markitup_tags.py and widgets.py |
Or #21, which I filed before this ticket was opened :P |
Working on it! Sorry for the extremely late response, burnout is real. Hope to update django-markitup for Django 2.0 some time during next week. |
Glad to have you back @zsiciarz |
Can I help to have this merged and released? |
Any progress with new release? Django 2.1 is already released, so would be nice to get new release with at least Django 1.11 and 2.0 support. |
FWIW: django 2.1 requires an additional change to two files. The patch mention previously (change reverse imports) gets rid of that '500' for 2.0, but with 2.1 there is another involving the 'render' kwarg being needed in the render routine. in widgets.py: twice at lines 14 and 71 in the latest on pypi as of this post. Once I moved to local execution, fixed the url import and this fix, Bob was, indeed, my uncle. This is explained in the very final line of the 2.1 release notes:
|
Unfortunately, this issue is still not fixed. Does anybody have a (temporary) solution? For instance another package which is a continuation of this package? |
@dgilge As a permanent solution I ended up switching to django-markupfield and was able to automatically make a migration after switching the field type. |
The CTPUG organisation has taken over maintaining django-markitup - https://github.com/CTPUG/django-markitup . We've released django-markitup 3.5.0 with support for Django 2.0, and will continue working on the other outstanding issues. |
When using django 2.0, I got this:
No module named 'django.core.urlresolvers'
inmarkitup.templatetags.markitup_tags
The text was updated successfully, but these errors were encountered: