Using Fabric3 or moving to Python3

[jatindhankhar]

I have no intention to question language or version choice. If it works with Python2 I am okay with it but most of the open source python tools are migrating to python 3 (Django for example).
Current version of aslo won't work with python3 becuase Fabric doesn't support python3 yet.
As per the docs

Fabric has not yet been tested on Python 3.x and is thus likely to be incompatible with that line of
development. However, we try to be at least somewhat forward-looking (e.g. using print() instead of print)
and will definitely be porting to 3.x in the future once our dependencies do.

We can look at Fabric3 which aims to support both 2.x and 3.x series.

It's more of an inquiry rather than a suggestion about what we want with aslo in the coming future. As long as it works and does the job, I am okay with either (or both) of it.
Thanks 😄

[quozl]

No problem, go ahead.

Issue of Python and Fabric version choice seems orthogonal to the significant problems experienced with activities.sugarlabs.org. If you have time at all to work on activities.sugarlabs.org language and version choices, then great, best of luck, but our needs as a community are more fundamental. You'll get more engagement with others if you can help with some of those needs. I'll raise specific issues here on GitHub.

[jatindhankhar]

Yeah sure 👍
Decisions like migrations and tech stack should be discussed with more people to carefully weigh down pros and cons. Most importantly whether community is happy about it or not.