The culprit line was just recently added 
in https://trac.sagemath.org/ticket/21821

could please the authors and reviewers of that ticket handle this problem ?

Le dimanche 13 novembre 2016 13:34:32 UTC+1, Frédéric Chapoton a écrit :
>
> after a make distclean and make, same problem, with a better log
>
> It seems that there is really some py3 incompatibility here:
>
> [sagelib-7.5.beta2] python -c "from sage_setup.autogen.pari import 
> rebuild; rebuild()"
> [sagelib-7.5.beta2] Traceback (most recent call last):
> [sagelib-7.5.beta2]   File "<string>", line 1, in <module>
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/src/sage_setup/autogen/pari/__init__.py", line 5, in 
> rebuild
> [sagelib-7.5.beta2]     G()
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/src/sage_setup/autogen/pari/generator.py", line 239, 
> in __call__
> [sagelib-7.5.beta2]     D = read_pari_desc()
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/src/sage_setup/autogen/pari/parser.py", line 83, in 
> read_pari_desc
> [sagelib-7.5.beta2]     with open(os.path.join(pari_share(), 'pari.desc')) 
> as f:
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/src/sage_setup/autogen/pari/parser.py", line 52, in 
> pari_share
> [sagelib-7.5.beta2]     out = gp.communicate("print(default(datadir))")[0]
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/local/lib/python3.5/subprocess.py", line 1068, in 
> communicate
> [sagelib-7.5.beta2]     stdout, stderr = self._communicate(input, endtime, 
> timeout)
> [sagelib-7.5.beta2]   File 
> "/home/chapoton/sage3/local/lib/python3.5/subprocess.py", line 1687, in 
> _communicate
> [sagelib-7.5.beta2]     input_view = memoryview(self._input)
> [sagelib-7.5.beta2] TypeError: memoryview: a bytes-like object is 
> required, not 'str'
> [sagelib-7.5.beta2] generate_py_source.mk:10 : la recette pour la cible « 
> sage/libs/pari/auto_gen.pxi » a échouée
>
>
> Le dimanche 13 novembre 2016 09:56:24 UTC+1, Dima Pasechnik a écrit :
>>
>>
>>
>> On Sunday, November 13, 2016 at 8:18:02 AM UTC, Frédéric Chapoton wrote:
>>>
>>> exact same problem after running ./configure. Should I try make 
>>> distclean ?
>>>
>> I'd have tried...
>>  
>>
>>>
>>> Le samedi 12 novembre 2016 22:16:41 UTC+1, Dima Pasechnik a écrit :
>>>>
>>>>
>>>>
>>>> On Saturday, November 12, 2016 at 8:43:57 PM UTC, Frédéric Chapoton 
>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> Trying to compile 7.5.b2 with python3 (using export SAGE_PYTHON3=yes), 
>>>>> I got now the following error:
>>>>>
>>>>> [sagelib-7.5.beta2] python -c "from sage_setup.autogen.pari import 
>>>>> rebuild; rebuild()"
>>>>> [sagelib-7.5.beta2] sys:1: RuntimeWarning: not adding directory '' to 
>>>>> sys.path since it's writable by an untrusted group.
>>>>> [sagelib-7.5.beta2] 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
>>>>> [sagelib-7.5.beta2] Traceback (most recent call last):
>>>>> [sagelib-7.5.beta2]   File "<string>", line 1, in <module>
>>>>> [sagelib-7.5.beta2] ImportError: No module named 
>>>>> sage_setup.autogen.pari
>>>>> [sagelib-7.5.beta2] generate_py_source.mk:10 : la recette pour la 
>>>>> cible « sage/libs/pari/auto_gen.pxi » a échouée
>>>>> [sagelib-7.5.beta2] make[4]: *** [sage/libs/pari/auto_gen.pxi] Erreur 1
>>>>> [sagelib-7.5.beta2] make[4] : on quitte le répertoire « 
>>>>> /home/chapoton/sage3/src »
>>>>> [sagelib-7.5.beta2] 
>>>>> ************************************************************************
>>>>> [sagelib-7.5.beta2] Traceback (most recent call last):
>>>>> [sagelib-7.5.beta2]   File "setup.py", line 111, in <module>
>>>>> [sagelib-7.5.beta2]     raise DistutilsSetupError("{} 
>>>>> failed".format(make_cmdline))
>>>>> [sagelib-7.5.beta2] DistutilsSetupError: make -f generate_py_source.mk 
>>>>> SAGE_SRC=/home/chapoton/sage3/src failed
>>>>>
>>>>> This seems to be different from what happens with previous versions of 
>>>>> sage, where the compilation of cython files started and failed on some 
>>>>> specific pyx files.
>>>>>
>>>>> Maybe there was a recent change that is not py3 compatible in the 
>>>>> build system ?
>>>>>
>>>>
>>>> have you ran ./configure first?
>>>>  
>>>>
>>>>>
>>>>> Frederic
>>>>>
>>>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to