I am compiling binary-pkg and encountered a deprecation warning.
The warning appeared when I invoked sage from command line.
(Technically, it was after messages of patching.)

The warning reads

```
.../quotient_ring.py:1350: DeprecationWarning: invalid escape sequence \Q
```

I read the file quotient_ring.py located at 
SageMath-9.1.beta8.app/Contents/Resources/sage/local/lib/python3.7/site-packages/sage/rings.

The description (line 1300--1350) of _macaulay2_init contains a line

```
Quotients of multivariate polynomial rings over `\QQ`, `\ZZ` and
```

So, I inserted 'r' before """ on line 1300. (""" -> r""").

After reinvocation of sage, the previous warning is gone.
Unfortunately, I cannot test the effect of the change on description.
I tried typing "_macaulay2_init_?". This did not work.

How can I test it? (Question 1.)

I thought  function name with "?" might not be the right syntax.
So, I tested "sqrt?". It gave me a series of deprecation warnings like

```
.../sessions.py:565: DeprecationWarning: invalid escape sequence \*
```

They make the screen to scroll one page.

These warnings for sessions.py are also descriptions of functions enclosed 
by """...""" pair inserted of r"""...""".
Yes, the recommended style was r"""..."" for description containing latex 
expressions.
The warnings for sessions.py might be regular expressions intended to be 
displayed by "function_name?"
or may be "*" are really escaped so that enclosing by r"""...""" and 
changing "\*" with "*" might help.
I do not have knowledge to distinguish these two.

(Question 2.) Is there any body who can tell which correction is suitable 
for sessions.py?
Option 1. """...""" -> r"""..."""
Option ". """... \*...""" -> r"""... *..."""

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c89c6fce-68cd-4404-8df3-1d9d4f5ff286%40googlegroups.com.

Reply via email to