Re: [sage-devel] Python3 comparing, an idea about deprecation

2017-11-06 Thread Jori Mäntysalo
On Mon, 6 Nov 2017, Jeroen Demeyer wrote: Speaking of comparisons and graphs: we'll need to fix https://trac.sagemath.org/ticket/22349 too at some point. Uh... There are propably at least 1000 doctest that needs to correct. And mmezzarobba is right: "in interactive use - - people want to see

Re: [sage-devel] Python3 comparing, an idea about deprecation

2017-11-06 Thread Jeroen Demeyer
On 2017-11-05 19:20, Jori Mäntysalo wrote: Is it possible to run min(L) in Python2 and at the same time check if it could be run in Python3 for given L? Reason: allow_multiple_edges() on generic_graph.py and keep_label='min' (or 'max'), can we have a nice deprecation? Speaking of comparisons a

Re: [sage-devel] Python3 comparing, an idea about deprecation

2017-11-06 Thread Jori Mäntysalo
On Mon, 6 Nov 2017, Jeroen Demeyer wrote: Is it possible to run min(L) in Python2 and at the same time check if it could be run in Python3 for given L? That depends mostly on what arguments you give to min(). 4) A mixture of the above What I was thinking is something like g = Graph([(1,2,'

Re: [sage-devel] Python3 comparing, an idea about deprecation

2017-11-06 Thread Jeroen Demeyer
On 2017-11-05 19:20, Jori Mäntysalo wrote: Is it possible to run min(L) in Python2 and at the same time check if it could be run in Python3 for given L? That depends mostly on what arguments you give to min(). Are we talking about 1) Standard Python types (str, int, ...) 2) Instances of sag

[sage-devel] Python3 comparing, an idea about deprecation

2017-11-05 Thread Jori Mäntysalo
Is it possible to run min(L) in Python2 and at the same time check if it could be run in Python3 for given L? Reason: allow_multiple_edges() on generic_graph.py and keep_label='min' (or 'max'), can we have a nice deprecation? -- Jori Mäntysalo