Le 20/10/2019 à 11:17, Vincent Delecroix a écrit :
Le 19/10/2019 à 13:19, David Roe a écrit :
I think the idea is that if a user's typing interactively then they don't
need a deprecation warning (since the behavior currently works). It's
more
important to show a user a warning if they have the deprecated
behavior in
a function they've written.
I don't agree with this behavior at all. A user typically wants to know
whether her commands are future-proof. Typical situation: I want to show
a colleague how to do this and that in sage cell. Damn I have a
different version on my computer! The commands that run smoothly in my
console fail in the sage cell.
And note that many people write Sage scripts with no function at all
(e.g. in a Sage notebook, or in a .sage file).
Finally, whatever choice of behavior is made, it should be consistent
between Python and Cython. See
https://trac.sagemath.org/ticket/28500
--
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/0724f70d-5547-5c48-7740-af339401e185%40gmail.com.
