search

CentreForDigitalHumanities / cookiecutter-webapp-deluxe

BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

Upgrade to Django 3 #9

Closed oktaal closed 4 years ago

oktaal commented 4 years ago

It's also straightforward to use 2 instead. They only difference with Django 3 is that the plugin django-revproxy breaks. I've sent a PR to them:

https://github.com/TracyWebTech/django-revproxy/pull/102

As Django 3 is scheduled to be released this December I think it would be good to use 3 for new developments.

jgonggrijp commented 4 years ago

So, is the plan to wait with merging this until December or until https://github.com/TracyWebTech/django-revproxy/pull/102 is merged, whichever happens last?

oktaal commented 4 years ago

I've reworked it so things should be passed through properly now. Even did away with npx. Currently it references the git-repository (master) of django-revproxy as they have merged the PR, but it isn't on PyPI yet. I think it's reasonably improbable that a project which will be started now will have to be completely finished before the release date of Django 3. This way any new project will be a bit more future-proof.

oktaal commented 4 years ago

Oh come on, Travis doesn't install the Django pre-release specified in the requirements.in for some reason. I give up for now, it works on my machine™. I'll look into it whenever a new project needs to be started.