Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Upgraded to Django 3.0 maybe? #103

Open
louisluhao opened this issue May 10, 2020 · 3 comments
Open

Upgraded to Django 3.0 maybe? #103

louisluhao opened this issue May 10, 2020 · 3 comments

Comments

@louisluhao
Copy link

louisluhao commented May 10, 2020

Or maybe have a separate repo for Django 3.0 template.

@niniack
Copy link

niniack commented May 10, 2020

Agreed! @ Project Maintainers If PRs for this are welcome, I'd like to take a shot at this!

@hkennyv
Copy link

hkennyv commented Jul 21, 2020

+1. Would love to see this. I'd be open to contributing as well since it looks like the last commit was in 2018

@niniack
Copy link

niniack commented Jul 23, 2020

I tried it out, seems that nothing actually had to be changed to reflect the move to Django 3. The comments/about/README just have to change to show that. There was virtually no difference in the template compared to other projects I've done without using a template.

The template seemed to make use of the package dj-database-url but this was missing in the Pipfile, which led to missing module error when deploying to Heroku. Threw that in there. Tested with the changes I made, works as expected!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants