Remove deprecated stuff related to Cython

[jdemeyer]

Remove deprecations from #22698, #22805, #23855, #24105.

Deprecate the script src/bin/sage-cython.

[jdemeyer]

New commits:

​108a42e

Remove deprecated stuff related to Cython

[vdelecroix]

(For the record: the 4 tickets have been closed for Sage 8.1 released in July 2017)

[jdemeyer]

Replying to vdelecroix:

(For the record: the 4 tickets have been closed for Sage 8.1 released in July 2017)

Not quite. #24105 is from Sage 8.2

[vdelecroix]

Replying to jdemeyer:

Replying to vdelecroix:

(For the record: the 4 tickets have been closed for Sage 8.1 released in July 2017)

Not quite. #24105 is from Sage 8.2

Which is bad as it was released 05/06/18... One year deprecation implies 5 more months.

[jdemeyer]

Replying to vdelecroix:

Which is bad as it was released 05/06/18... One year deprecation implies 5 more months.

No, we are both wrong :-)

#22805 is from Sage 8.0

#22698, #23855, #24105 are from Sage 8.1

So this should be fine.

[embray]

Maybe not for this ticket, but there's a patch in Debian related to this that I think would be worth incorporating into Sage somehow:

sage/src/sage/interfaces/singular.py

@@ -2264 +2264 @@
     node_names.clear()
 
     import os
-    singular_docdir = os.environ['SINGULARPATH']+"/../info/"
+    singular_docdir = "/usr/share/doc/singular/"
 
     new_node = re.compile(r"File: singular\.hlp,  Node: ([^,]*),.*")
     new_lookup = re.compile(r"\* ([^:]*):*([^.]*)\..*")

sage/src/sage/misc/cython.py

@@ -323 +323 @@
     args = ['-w','-O2'] + args
     libdirs = cblas_library_dirs
 
+    # Add Singular directories to includes
+    if "singular" in s or "pynac" in s:
+        import pkgconfig
+        inc.extend(sorted(set(pkgconfig.parse("Singular")["include_dirs"])))
+
     # Add cysignals directory to includes
     for path in sys.path:
         cysignals_path = os.path.join(path, "cysignals")

sage/src/sage/env.py

@@ -187 +187 @@
     else:
         extension = "so"
     # library name changed from libsingular to libSingular btw 3.x and 4.x
-    SINGULAR_SO = SAGE_LOCAL+"/lib/libSingular."+extension
+    SINGULAR_SO = "/usr/lib/%s/libsingular-Singular-4.1.1.so" % sysconfig.get_config_var('MULTIARCH')
 
 _add_variable_or_fallback('SINGULAR_SO', SINGULAR_SO)
 

sage/src/sage/misc/compat.py

@@ -87 +87 @@
     EXAMPLES::
 
         sage: from sage.misc.compat import find_library
-        sage: find_library('Singular')
+        sage: find_library('singular-Singular')
         '...Singular...'
 
     """

I think that this demonstrates that there needs to be a better way to customize where sage looks for bits of Singular (the library, as well as its docs and include files).

[embray]

Hooray for getting rid of cruft.

[vbraun]

sage -t --long src/sage/tests/cmdline.py
**********************************************************************
File "src/sage/tests/cmdline.py", line 412, in sage.tests.cmdline.test_executable
Failed example:
    print(err)
Expected:
    Traceback (most recent call last):
    ...
    RuntimeError: refusing to run doctests...
Got:
    sys:1: RuntimeWarning: not adding directory '' to sys.path since everybody can write to it.
    Untrusted users could put files in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory
    Traceback (most recent call last):
      File "/mnt/disk/home/release/Sage/src/bin/sage-runtests", line 163, in <module>
        err = DC.run()
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1200, in run
        self.test_safe_directory()
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 643, in test_safe_directory
        .format(os.getcwd()))
    RuntimeError: refusing to run doctests from the current directory '/mnt/disk/home/release/.sage/temp/volker/30915/dir_Gy_O0N/test' since untrusted users could put files in this directory, making it unsafe to run Sage code from
    <BLANKLINE>
**********************************************************************
File "src/sage/tests/cmdline.py", line 417, in sage.tests.cmdline.test_executable
Failed example:
    print(err)
Expected:
    Traceback (most recent call last):
    ...
    RuntimeError: refusing to run doctests...
Got:
    sys:1: RuntimeWarning: not adding directory '' to sys.path since everybody can write to it.
    Untrusted users could put files in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory
    Traceback (most recent call last):
      File "/mnt/disk/home/release/Sage/src/bin/sage-runtests", line 163, in <module>
        err = DC.run()
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1200, in run
        self.test_safe_directory()
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 643, in test_safe_directory
        .format(os.getcwd()))
    RuntimeError: refusing to run doctests from the current directory '/mnt/disk/home/release/.sage/temp/volker/30915/dir_Gy_O0N/test' since untrusted users could put files in this directory, making it unsafe to run Sage code from
    <BLANKLINE>
**********************************************************************
1 item had failures:
   2 of 251 in sage.tests.cmdline.test_executable
    [250 tests, 2 failures, 41.71 s]
----------------------------------------------------------------------
sage -t --long src/sage/tests/cmdline.py  # 2 doctests failed
----------------------------------------------------------------------
Total time for all tests: 41.8 seconds

[jdemeyer]

That error doesn't seem related to this ticket at all.