Support for Django 1.11.x #22
Comments
|
Installing on new django 2.1.1 will downgrade it. |
|
What do you mean with "compiled" ? Javascript asset minification ? |
|
compiled as in call python setyp.py with modified code... Currently the project is aimed at Django 1.X which is OLD.. But I guess it may simply not work until the project is verified to work with Django 2.x. |
|
You could try support with the tests, just changing the tox config in a development environment: https://djangocodemirror.readthedocs.io/en/latest/development.html But i'm pretty sure it won't work, since Django 1.11 there was some incompatible changes that breaks the widget i should have fixed before even thinking to Django 2.x |
|
are these fixes planned for some point in time? or is the project considered abandoned? |
|
It's on the way, i got some tests to fix with Django 1.11, Django 2.0 should not take more time. This should be released to a new major version at the end of the week. |
* Rewrite package to use 'setup.cfg'; * Add support for Django 1.11, Django 2.0 and Django 2.1, close #22; * Drop support for Django 1.8 and 1.9; * Django 1.11 support is the last one for Python2; * Change old demo project to more cleaner sandbox; * Change widget to use new Django widget API;
* Rewrite package to use 'setup.cfg'; * Add support for Django 1.11, Django 2.0 and Django 2.1, close #22; * Drop support for Django 1.8 and 1.9; * Django 1.11 support is the last one for Python2; * Change old demo project to more cleaner sandbox; * Change widget to use new Django widget API;
Add support for Django>=1.11. Close #22
|
Who hoo?! Thanks for the amazing update :-) Going to try it now! |
No description provided.
The text was updated successfully, but these errors were encountered: