On Wednesday, April 8, 2020 at 3:30:44 PM UTC-7, Matthias Koeppe wrote: > > On Wednesday, April 8, 2020 at 7:53:07 AM UTC-7, rana-aerea rossa wrote: >> >> I need someone to tell me where to propose three kinds of changes of >> Sagemath. >> (1) I guess Sagemath misses change log for some time. >> > > See https://trac.sagemath.org/ticket/22176 for a proposal based on a > discussion 3 years ago ( > https://groups.google.com/forum/?hl=en#!topic/sage-devel/81qsOpoOKMM). > > An outline of the python2/python3 situation is on the Sage Wiki at > https://wiki.sagemath.org/Python3-Switch; this is linked from the front > page of sagemath.org > > There are many minor changes so report on this issue might eat-up forums >> if I we report them one by one. >> > > That would be too much for sage-devel, but it is not a problem to create > many tickets on trac. > > I am trying to find a way of silencing deprecation warnings on "..\Q..." >> and so on. >> > > It is better to just fix them. Usually only a literal string "...." needs > to be changed to a raw literal r"....". >
I don't think there are many left in the Sage library itself. Some come from Python packages being called by Sage; for example, IPython.core.inputtransformer does this (fixed in more recent versions). We should certainly fix the ones within Sage, but then we should silence the others (and report them upstream). -- John -- 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/754106ee-1582-4099-b72c-75b3db4bcff6%40googlegroups.com.
