This repository has been archived by the owner on Jan 26, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Coordinate with Portal group re: moving to Django 1.8 LTS #12
Comments
@rosariorobinson @tapasweni-pathak @ana-balica @vubo @jayesh92 Rose, I'm wondering if it would make sense to use Python 3 which the Systers Portal project uses? Thoughts anyone? |
Hi Carol, Rose wanted VMS to be integrated with Portal eventually, so I think it would make sense to port to Python 3. It would be better to port earlier than later so there's less code to port over. |
@Nerdylicious Thanks for the input. I agree that sooner is better than later. |
Hi Carol, I too believe, we should port to Python 3 early, as later more code fixing and porting will be required. |
Merged
@willingc thank you! I ported all code to Python 3 and I'm using Python 3.4 and Django 1.8.3 now. |
Awesome @vubo. 😄 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Django 1.8 is a long term supported release (LTS). It would be useful to upgrade the code bases to Django 1.8 since it will have longer term support than the current version used. https://www.djangoproject.com/download/ for details.
The text was updated successfully, but these errors were encountered: