Unable to make sage after upgrading

[SIDDHARTH SINGH]

I am unable to build sage after a recent upgrade (Arch). On investigation, the line that is giving the error is "from pip._vendor.six import iteritems". Note that the same is not raising an error if executed from any other directory but when executing from "/src/sage/misc/" it raises the following error

ImportError: cannot import name 'iteritems' from 'six' (/home/sidd/Projects/gsoc/sage/src/sage/misc/six.py)

This line is executed in the "/src/sage/misc/package.py -> pip_installed_packages" when this line of code is executed

proc = subprocess.Popen(

            [sys.executable, "-m", "pip", "list", "--no-index", "--format", "json"],

            stdout=subprocess.PIPE,

            stderr=devnull,

        )

While it does not raise any error during make, the stderr contains the traceback. The stdout is then just an empty string which raises error when parsing it as a json dict. Is there any fix for this?

[Dima Pasechnik]

This might well be fixed in the latest beta.
Did you try it?

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/e062fb58-6c66-41e2-88bb-b19bd6be9eb2%40googlegroups.com.

[SIDDHARTH SINGH]

It doesn't seem fixed in 9.1.beta7 Is there any other branch which is more recent. I am currently working on #29347 and this is not letting me build. It is giving me an error in the same line but this time I am not able to replicate it by manual running. Attaching the logs

On Sunday, April 12, 2020 at 6:37:33 AM UTC+5:30, Dima Pasechnik wrote:

This might well be fixed in the latest beta.
Did you try it?

On Sun, Apr 12, 2020 at 12:59 AM SIDDHARTH SINGH
<f201...@pilani.bits-pilani.ac.in> wrote:
>
> I am unable to build sage after a recent upgrade (Arch). On investigation, the line that is giving the error is "from pip._vendor.six import iteritems". Note that the same is not raising an error if executed from any other directory but when executing from "/src/sage/misc/" it raises the following error
> ImportError: cannot import name 'iteritems' from 'six' (/home/sidd/Projects/gsoc/sage/src/sage/misc/six.py)
>
> This line is executed in the "/src/sage/misc/package.py -> pip_installed_packages" when this line of code is executed
>
> proc = subprocess.Popen(
>             [sys.executable, "-m", "pip", "list", "--no-index", "--format", "json"],
>             stdout=subprocess.PIPE,
>             stderr=devnull,
>         )
>
>
> While it does not raise any error during make, the stderr contains the traceback. The stdout is then just an empty string which raises error when parsing it as a json dict. Is there any fix for this?
>
>
> --
> 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-...@googlegroups.com.

[Matthias Koeppe]

From one of your logfiles:

[sage_conf] Installing 
[sage_conf] Traceback (most recent call last):
[sage_conf]   File "setup.py", line 1, in <module>
[sage_conf]     from setuptools import setup
[sage_conf]   File "/home/sidd/Projects/gsoc/sage/local/lib/python3.7/site-packages/setuptools/__init__.py", line 18, in <module>
[sage_conf]     from setuptools.dist import Distribution, Feature
[sage_conf]   File "/home/sidd/Projects/gsoc/sage/local/lib/python3.7/site-packages/setuptools/dist.py", line 31, in <module>
[sage_conf]     from setuptools import windows_support
[sage_conf]   File "/home/sidd/Projects/gsoc/sage/local/lib/python3.7/site-packages/setuptools/windows_support.py", line 2, in <module>
[sage_conf]     import ctypes
[sage_conf]   File "/home/sidd/Projects/gsoc/sage/local/lib/python3.7/ctypes/__init__.py", line 7, in <module>
[sage_conf]     from _ctypes import Union, Structure, Array
[sage_conf] ImportError: libffi.so.6: cannot open shared object file: No such file or directory
[sage_conf] Error: could not determine package name

Looks like the python3 installation in SAGE_LOCAL is broken, perhaps because of an update of the system libraries - libffi is coming from the OS in your case. I suggest build 9.1.rc0 from scratch (in a new tree or after make distclean).