Skip to content
This repository has been archived by the owner on Jan 26, 2021. It is now read-only.

Coordinate with Portal group re: moving to Django 1.8 LTS #12

Closed
willingc opened this issue May 30, 2015 · 7 comments
Closed

Coordinate with Portal group re: moving to Django 1.8 LTS #12

willingc opened this issue May 30, 2015 · 7 comments

Comments

@willingc
Copy link
Contributor

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.

@willingc
Copy link
Contributor Author

willingc commented Jun 5, 2015

@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?

@Nerdylicious
Copy link
Contributor

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.

@willingc
Copy link
Contributor Author

willingc commented Jun 9, 2015

@Nerdylicious Thanks for the input. I agree that sooner is better than later.

@tapaswenipathak
Copy link
Contributor

Hi Carol,

I too believe, we should port to Python 3 early, as later more code fixing and porting will be required.

@willingc
Copy link
Contributor Author

@tapasweni-pathak 👍

@vubo vubo mentioned this issue Jul 9, 2015
@vubo
Copy link
Contributor

vubo commented Jul 9, 2015

@willingc thank you! I ported all code to Python 3 and I'm using Python 3.4 and Django 1.8.3 now.

@tapaswenipathak
Copy link
Contributor

Awesome @vubo. 😄
Closing this then.

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

4 participants