These are chat archives for fossasia/open-event-server

28th
Apr 2016
Justin Lee
@juslee
Apr 28 2016 08:29
question: is there a reason why we aren't using Python 3.5?
Rafał Kowalski
@rafalkowalski
Apr 28 2016 13:26
@juslee i suppose that no ;p
Justin Lee
@juslee
Apr 28 2016 13:31
can we use python 3.5 then? instead of 2.7?
Shivam Mamgain
@shivamMg
Apr 28 2016 13:41
+1 for python3. we would pretty much be rewriting the entire server, would be better with python3.
Justin Lee
@juslee
Apr 28 2016 13:48
is it a rewrite? :P
Shivam Mamgain
@shivamMg
Apr 28 2016 13:49
You know what, lets create a new repo... :P
Justin Lee
@juslee
Apr 28 2016 13:50
HAHAHAHAHA whistle i don't know.
Arnav Gupta
@championswimmer
Apr 28 2016 14:45
In a way a rewrite can be helpful. With all the previous work, we know what all data structures we need. What all apis to provide, by which keys we need to search or sort.
Rewrite won't take as much time as it took to build first time.
Plus we didn't completely work with the hosted + diy model (like wordpress) in mind last year.
Saptak Sengupta
@SaptakS
Apr 28 2016 14:54
Yeah.. And if we migrate to python 3.5 then it would be almost a rewrite.. Many of the syntax I believe are different. Anyways I agree with Arnav Gupta..
Aditya Vyas
@aditya1702
Apr 28 2016 18:16
+1 for rewrite
Duke Leto
@leto
Apr 28 2016 18:17
in general I like Python 3 and have used it in the past. My question is: what benefit do we get from it?
if we are rewriting the front-end with django and the whole project in python 3, that is a lot of change that needs to be coordinated, so people aren't waiting on others
Aditya Vyas
@aditya1702
Apr 28 2016 18:21
@leto I am reading the doc link you sent above. I am assuming the rewrite wont take long. So cant we carry out the changes we need to do in the server and then do a rewrite?
Duke Leto
@leto
Apr 28 2016 18:22
@aditya1702 in theory. I suggest making a branch and attempting to convert to python 3. That script will get you 90% of the way there but you may need to make some manual modifications
our code is relatively simple and doesn't use a lot of the features that have changed in Python 3, like iterators and how byte strings work
some of the python libraries we use might not work on 3, potentially
Aditya Vyas
@aditya1702
Apr 28 2016 18:25
I will try out testing the 2to3
Duke Leto
@leto
Apr 28 2016 18:25
sounds good, let us know what you find
Aditya Vyas
@aditya1702
Apr 28 2016 18:26
Yes :smile: @leto did you talk with @creativepsyco regarding the API keys issue? I was wondering what we could do about that issue
Duke Leto
@leto
Apr 28 2016 18:27
well @creativepsyco is not really involved much now, so it is up to us to decide
Aditya Vyas
@aditya1702
Apr 28 2016 18:27
Ok
Duke Leto
@leto
Apr 28 2016 18:30
it sounds like people want to use oauth. I have done that in flask but not django
Rafał Kowalski
@rafalkowalski
Apr 28 2016 20:04
@/all will we create a new branch of repository?
Duke Leto
@leto
Apr 28 2016 20:28
branches are good
Rafał Kowalski
@rafalkowalski
Apr 28 2016 20:29
but i suppose that all structure of repo will be changed
Duke Leto
@leto
Apr 28 2016 20:59
all things are always changing :)
especially code
Saptak Sengupta
@SaptakS
Apr 28 2016 21:01
@leto :+1: