I don't think clean_stale_files is to blame. It is removing the build
files. What is wrong is that the relevant file are *not* installed
before. I guess it is a problem in the install.run() method.
Vincent
On 25/04/2017 21:14, Frédéric Chapoton wrote:
Thanks for the hint, Salvatore !
Indeed,
Thanks for the hint, Salvatore !
Indeed, the line "self.clean_stale_files()" inside src/setup.py probably
does something wrong, maybe confusing python2 and python3 ?
If somebody else feels concerned, please help to investigate the issue.
Frederic
Le jeudi 20 avril 2017 16:29:46 UTC+2, Salvator
Indeed if one comments line 847 in src/setup.py the files looks to be there.
Sage crashes anyway but now:
VulK@bunion /mnt/backup/sage-py3 (git)-[my_py3] % ./sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything
It looks to me that the various .so files get compiled but then removed just
before the build finishes. Here is a snippet of the log:
byte-compiling
/mnt/backup/sage-py3/local/lib/python3.5/site-packages/sage/stats/r.py to
r.cpython-35.pyc
byte-compiling
/mnt/backup/sage-py3/local/lib/python3
~/sage3/src/build$ find -name "*.so"
returns nothing :(
Le jeudi 20 avril 2017 09:35:50 UTC+2, vdelecroix a écrit :
>
> Can you look at SAGE_ROOT/src/build and try to find is there is a .so
> there. For example
>
> $ find $(sage -root)/src/build -name "*.so"
>
> (normally there should be, the
Can you look at SAGE_ROOT/src/build and try to find is there is a .so
there. For example
$ find $(sage -root)/src/build -name "*.so"
(normally there should be, the cythonization process put stuff there)
On 20/04/2017 09:07, Frédéric Chapoton wrote:
STOP ! you should export SAGE_PYTHON3=yes
L
STOP ! you should export SAGE_PYTHON3=yes
Le jeudi 20 avril 2017 09:02:54 UTC+2, Frédéric Chapoton a écrit :
>
> Really 355 ? More like 20, but I agree that it is a mess.
>
> This is my own experimental branch, not for evereybody's eyes.. It is made
> from 22764, 22756, 22305 and 22775
>
> plus o
Really 355 ? More like 20, but I agree that it is a mess.
This is my own experimental branch, not for evereybody's eyes.. It is made
from 22764, 22756, 22305 and 22775
plus one own commit that takes care (not in a good way) of the last two
calls to cmp() in pyx files.
Frederic
Le jeudi 20 avr
Waiting for make... I have nothing to do in order that Python3 is used
instead of Python2?
On 20/04/2017 08:52, Frédéric Chapoton wrote:
Salut,
you have to apply first : public/experimental_python3_v0
then the ticket 22775 (new conway_polynomial
package) https://trac.sagemath.org/ticket/22775
Why do you have 355 commits on public/experimental_python3_v0?! It is
hard to find its way...
On 20/04/2017 08:52, Frédéric Chapoton wrote:
Salut,
you have to apply first : public/experimental_python3_v0
then the ticket 22775 (new conway_polynomial
package) https://trac.sagemath.org/ticket/22
Salut,
you have to apply first : public/experimental_python3_v0
then the ticket 22775 (new conway_polynomial
package) https://trac.sagemath.org/ticket/22775
Frederic
Le jeudi 20 avril 2017 08:40:33 UTC+2, vdelecroix a écrit :
>
> Salut Frédéric,
>
> Then this is the problem. Cython should gen
Salut Frédéric,
Then this is the problem. Cython should generate .so files for each .pyx
present in the Sage source code (which should be in the site-packages of
Python3). If you provide an explicit branch with your "hacks" to get
Sage compiled I might be able to provide more help.
Vincent
Salut,
There is no lazy_import.so in local/lib/python3.5/site-packages/sage/misc
folder (and in fact no .so file at all there)
And I get
Python 3.5.1 (default, Apr 16 2017, 11:35:45)
Type "copyright", "credits" or "license" for more information.
IPython 5.1.0 -- An enhanced Interactive Pytho
Do you have the corresponding (cython) library
SAGE_ROOT/local/lib/python3.5/site-packages/sage/misc/lazy_import.so
If so could you try (inside a python3 shell)
import sage.misc.lazy_import
that should give you a more precise error.
Vincent
On 19/04/2017 14:57, Frédéric Chapoton wrote
Here it is (once again, the failure is related to a cython module):
(sage-sh) chapoton@pc-chapoton:sage3$ python3
Python 3.5.1 (default, Apr 7 2017, 12:17:26)
[GCC 5.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sage.all
Traceback (most recent c
Indeed, could you try
$ sage -sh
(sage-sh) $ python3
>>> import sage.all
Vincent
On 19/04/2017 13:11, Frédéric Chapoton wrote:
Hello,
I get nothing from "ls local/lib/python2.7/site-packages/sa*"
and what looks like a correct full sage
in local/lib/python3.5/site-packages/sage
The pro
Hello,
I get nothing from "ls local/lib/python2.7/site-packages/sa*"
and what looks like a correct full sage
in local/lib/python3.5/site-packages/sage
The problem may come from "./sage" calling a python2.7 version ?
Frederic
Le mercredi 19 avril 2017 10:58:53 UTC+2, vdelecroix a écrit :
>
> H
Hi Frédéric,
Can you check what are inside
SAGE_ROOT/local/lib/python2.7/site-packages/sage
SAGE_ROOT/local/lib/python3.5/site-packages/sage
Vincent
On 18/04/2017 21:25, Frédéric Chapoton wrote:
Dear all,
I just managed (using tricks to avoid a few remaining issues in
cythonization and p
Dear all,
I just managed (using tricks to avoid a few remaining issues in
cythonization and packages) to get make succeed in building sage with
SAGE_PYTHON3=yes
Sadly, but not unexpectedly, sage then crashes at startup. Apparently, it
cannot not find/import any cython extension..
Frédéric
Her
19 matches
Mail list logo
