Yes, cmp is a big mess ;
see https://trac.sagemath.org/query?status=!closed&component=python3
for what has been done and what remains
Frédéric
Le dimanche 9 avril 2017 17:05:44 UTC+2, Marco Cognetta a écrit :
>
> I see that there has been work on converting print statements and simple
> stuff
On Sunday, April 9, 2017 at 10:05:44 AM UTC-5, Marco Cognetta wrote:
>
> I see that there has been work on converting print statements and simple
> stuff like that to be python 3 compatible. What are the other steps
> involved in fully supporting python 3 that are still underway (or haven't
>
On Sunday, April 9, 2017 at 8:00:15 AM UTC-5, Andrew wrote:
>
> Is there a significant change behind going from version 7.6 to 8.0?
> Andrew
>
> The major change there will be to start using the Jupyter notebook as the
default instead of the SageNB. Python3 will be a later major version bump.
B
I see that there has been work on converting print statements and simple stuff
like that to be python 3 compatible. What are the other steps involved in fully
supporting python 3 that are still underway (or haven't been started)?
--
You received this message because you are subscribed to the Go
Is there a significant change behind going from version 7.6 to 8.0?
Andrew
On Saturday, 8 April 2017 03:14:01 UTC+10, vdelecroix wrote:
>
> On 07/04/2017 19:03, John H Palmieri wrote:
> > Python 3 is also built and installed by default in Sage, at least in
> recent
> > development versions, for
On 07/04/2017 19:03, John H Palmieri wrote:
Python 3 is also built and installed by default in Sage, at least in recent
development versions, for use by developers trying to make Sage compatible
with Python 3.
Indeed, you can use it
$ sage -sh -c "python3"
Python 3.5.1 (default, Apr 7 2017, 0
Python 3 is also built and installed by default in Sage, at least in recent
development versions, for use by developers trying to make Sage compatible
with Python 3.
--
John
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
Not yet, but Frédéric Chapoton has been doing a lot to try and make Sage
Python3 compatible. So we now have the option to try to compile with
Python3. We would welcome any assistance in trying to make this transition.
Best,
Travis
On Friday, April 7, 2017 at 9:15:16 AM UTC-5, aishen wrote:
>
>