Alex,
Can you post it here? https://goo.gl/forms/PV3SV8opzBnb1eqw2
Sameer
On Jan 24, 2018 12:37 PM, "Sameer Verma" wrote:
On Wed, Jan 24, 2018 at 8:28 AM, Alex Perez wrote:
> Sameer,
>
> Apologies for top-posting.
>
> For 2018, I would really like to see Sugar Labs get behind and commit to
> g
On Wed, Jan 24, 2018 at 8:28 AM, Alex Perez wrote:
> Sameer,
>
> Apologies for top-posting.
>
> For 2018, I would really like to see Sugar Labs get behind and commit to
> getting the core of Sugar working fully with Python 3. I personally believe
> this is critical to its long(er) term success, as
Hi
I agree with the general idea - this is going to only become more painful
the longer it is left undone, and if not done, will mean the end of the
python codebase. That might be acceptable, given the maturation of
Sugarizer.
Perhaps its worth having the Sugar core and toolkit part (vs the Sugar
Sameer,
Apologies for top-posting.
For 2018, I would really like to see Sugar Labs get behind and commit to
getting the core of Sugar working fully with Python 3. I personally
believe this is critical to its long(er) term success, as Python 2
continues be deprecated. Python 2 will not be supp