See
https://trac.sagemath.org/ticket/28500
Le 20/10/2019 à 08:36, David Roe a écrit :
I don't mind changing the behavior, I was just trying to explain why it's
currently as is. If we do make a change, we'll probably have to detect an
interactive session as a special case so that we can keep the current
behavior when called from a function.
David
On Sun, Oct 20, 2019 at 4:45 AM Simon King <simon.k...@uni-jena.de> wrote:
Hi David,
On 2019-10-19, David Roe <roed.m...@gmail.com> wrote:
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 like that idea. If they write code, I suppose many people
test their code in an interactive session while writing it. So, it would
be fair to show them during the interactive session that the code
they're about to write is deprecated.
Best regards,
Simon
--
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/qoh6qq%2439ev%241%40blaine.gmane.org
.
--
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/1ce72b00-8067-0d41-67bc-2cbf7f0d8d0d%40gmail.com.
