On Thursday, August 29, 2019 at 7:15:51 AM UTC-7, Frédéric Chapoton wrote:
>
> Hello
>
> Somebody (else) should make sure that every single remaining piece of
> python2 is removed from a python3 sage. In particular, we should not build
> python2 at all.
>
See
On Thu, Aug 29, 2019 at 6:02 PM Samuel Lelievre
wrote:
> Possibly somewhat related (sorry if not): after building Sage
> for Python 3, running `sage -t` lets the doctesting framework
> decide what to set `optional` to, and apparently it uses
> "python2" rather than "python3"; is this the desired
Possibly somewhat related (sorry if not): after building Sage
for Python 3, running `sage -t` lets the doctesting framework
decide what to set `optional` to, and apparently it uses
"python2" rather than "python3"; is this the desired behaviour?
$ ./sage --python --version
Python 3.7.3
$ ./sage -t
Le mercredi 28 août 2019 21:29:29 UTC+2, Eric Gourgoulhon a écrit :
>
>
> You are perfectly right: "check" would be more appropriate than "verbose"
> in this context.
> I'll open a ticket for this and make "check=True" the default.
>
This is now https://trac.sagemath.org/ticket/28422.
Eric.
Hello
Somebody (else) should make sure that every single remaining piece of
python2 is removed from a python3 sage. In particular, we should not build
python2 at all.
Frédéric
Le jeudi 29 août 2019 12:35:46 UTC+2, Simon King a écrit :
>
> Hi Dima,
>
> On 2019-08-29, Dima Pasechnik > wrote:
Thanks for all of the thoughtful replies.
I don't have time to rewrite the config script any time soon.
According to the libtool documentation, it is supposed to be usable
without relying on automake.
NTL's config script allows you to override the default libtool with a
system libtool,
so that
Hi Dima,
On 2019-08-29, Dima Pasechnik wrote:
> is this python2 from your OS, or from Sage's installation?
>From Sage's installation (apparently Sage-with-py-3 also builds
python-2):
(sage-sh) king@klap:~$ which python
/home/king/Sage/git/py3/local/bin/python
(sage-sh) king@klap:~$
It is sort of normal. [PEP0394] used to say that python
should be an alias for python2. But now it says that it
should either be python2 or python3.
Sage just follows the logic that was in place.
[PEP0394] https://www.python.org/dev/peps/pep-0394/
Vincent
Le 29/08/2019 à 12:00, Simon King a
is this python2 from your OS, or from Sage's installation?
On Thu, 29 Aug 2019 13:00 Simon King, wrote:
> Hi!
>
> The following happens with a Py-3 build of Sage: I open a sage-shell,
> and then I get
> (sage-sh) king@klap:src$ sage --python --version
> Python 3.7.3
> (sage-sh)
Hi!
The following happens with a Py-3 build of Sage: I open a sage-shell,
and then I get
(sage-sh) king@klap:src$ sage --python --version
Python 3.7.3
(sage-sh) king@klap:src$ python --version
Python 2.7.15
Is it expected that the default python version in a py-3 install is a
py-2?
Best
El jueves, 29 de agosto de 2019, 0:06:49 (UTC+2), Dima Pasechnik escribió:
>
>
> > Relying on patched bundled copies of dependencies is very much frowned
> upon by distros. It would be much preferable to make this work with
> unmodified libtool, which may be provided by the distribution.
>
>
11 matches
Mail list logo
