Hey @jonatoni , @jflory7 , I am an outreachy applicant. I request to work on this task.

Hii @jonatoni @jflory7
I am an outreachy applicant and would like to work on this issue if @joycenamuli is not. :)

@joycenamuli @sanjana11147 I need to look into this one further. I haven't had a chance to get more context yet. Please look at other tickets for now. I suggest #100 and #103 as starting points.

@jflory7 Our project is using Python 2.7.15 and I don't see how the above would fit in our project.

@feisal Could you give a more details on this?

@jflory7 Our project is using Python 2.7.15 and I don't see how the above would fit in our project.

@shraddhaag My suspicion is we probably need to open a new ticket for migrating the project from Python 2 to Python 3, but I haven't had a chance to dig in deeper yet.

@jflory7 As support for both Python 2.7 and Django 1.11 ends in 2020, (more on this here) I think we should upgrade both of them, Python to 3.7 and Django to 2.1. If you find both of them valid, I'll open a ticket for the same

@shraddhaag yes, we had this on our roadmap for a while but we didn't have the chance to do it. Even though, I think we should fix this when the Outreachy student will start the internship.

@shraddhaag but feel free to open a ticket about it :smile: Thanks

@shraddhaag I've been meaning to open a new ticket for Python 2 => Python 3 migration for a week. :sweat_smile: If you could open a new ticket, that would be awesome. We can close this ticket as moved to the new one.

Even though we use python 2.7, the documentation has a prerequisite 'Python (version >= 3.5)'. We should change it for the time being until we migrate to Python 3.

I am closing this ticket since #150 better captures the work required to fix this issue.

Even though we use python 2.7, the documentation has a prerequisite 'Python (version >= 3.5)'. We should change it for the time being until we migrate to Python 3.

@sanjana11147 Good catch. We can change it until #150 is closed. Feel free to submit a pull request if you have time that does the following:

1. Change required Python version to Python 2
2. Add a ..note: to the docs to mention plan to eventually migrate to Python 3, add a link to ticket #150

Is this something you want to do?

I am closing this ticket since #150 better captures the work required to fix this issue.

Even though we use python 2.7, the documentation has a prerequisite 'Python (version >= 3.5)'. We should change it for the time being until we migrate to Python 3.

@sanjana11147 Good catch. We can change it until #150 is closed. Feel free to submit a pull request if you have time that does the following:

Change required Python version to Python 2
Add a ..note: to the docs to mention plan to eventually migrate to Python 3, add a link to ticket #150

Is this something you want to do?

Yeah sure @jflory7 I would do that.

Yeah sure @jflory7 I would do that.

@sanjana11147 Great, feel free to send a pull request for this. :thumbsup: