On Sunday, September 1, 2019 at 12:14:51 PM UTC-7, Thierry
(sage-googlesucks@xxx) wrote:
>
> Hi,
>
> it seems to me that Python 3 migration should not only be a syntax
> adaptation (like print('blah')), unicode, or the mitigation of issues
> related to the fact that different objects are not always comparable.
>
> Indeed, there are opportunities there. However, large overhaul projects
have a mixed track record of succeeding, and py2-py3 migration needs to
happen: we can't afford to screw it up. So I'm in favor of changing the
logic in sage to better align with py3 philosophy but I'm not in favour of
doing it together with migrating to py3. We should do that in whatever way
makes for the best manageable transition. Once we're on py3, we don't have
to worry about py2 compatibility anymore, so changing to py3 semantics will
be easier to accomplish.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/c6798142-8f4e-41ca-9efe-2bc5f7758e3d%40googlegroups.com.
