Re: [sage-devel] python3 (not yet, and not for soon)

On Mon, Aug 7, 2017 at 12:45 PM, Jeroen Demeyer wrote: > On 2017-08-07 12:00, François Bissey wrote: >> >> Looking at this more closely. Why isn’t the “bytes” conversion >> done earlier - before checking that the file exists. > > > +1 > > I know that Erik Bray will

Re: [sage-devel] python3 (not yet, and not for soon)

The core-dumped is supposed to be fixed by the pynac upgrading ticket https://trac.sagemath.org/ticket/23325 . So it does not require any further work hopefuly. Le lundi 7 août 2017 11:54:14 UTC+2, Erik Bray a écrit : > > Hi Frédéric, all, > > Regarding > > > * There remains to make a proper

Re: [sage-devel] python3 (not yet, and not for soon)

On 2017-08-07 12:00, François Bissey wrote: Looking at this more closely. Why isn’t the “bytes” conversion done earlier - before checking that the file exists. +1 I know that Erik Bray will disagree with this, but I would advocate to use "bytes" as much as possible when dealing with

Re: [sage-devel] python3 (not yet, and not for soon)

Hi, Le 07/08/2017 à 11:54, Erik Bray a écrit : > I'm working on a better solution to this as part of a more general > reworking of how Sage's dist handles dependencies that can be > fulfilled by multiple packages (in this case the dependency being > 'python'--specifically the Python used for

Re: [sage-devel] python3 (not yet, and not for soon)

Looking at this more closely. Why isn’t the “bytes” conversion done earlier - before checking that the file exists. Is there a reason why the string is converted before dl-opening the library? > On 7/08/2017, at 18:51, François Bissey wrote: > >> On 7/08/2017, at 18:23,

Re: [sage-devel] python3 (not yet, and not for soon)

Hi Frédéric, all, Regarding > * There remains to make a proper python3 install setup, in order to make it > easier to debug. Currently, "make" with "SAGE_PYTHON3=yes" always rebuilds > everything, which is *very annoying*. Happily, using only "sage -b" take > much less time. For instance, an

Re: [sage-devel] python3 (not yet, and not for soon)

> On 7/08/2017, at 18:23, Frédéric Chapoton wrote: > > Thanks ! Could you make a ticket for this change to singular, please ? > Sure will do. > And building the doc is not yet something that could be tried with hope of > success, I think. Maybe better after

Re: [sage-devel] python3 (not yet, and not for soon)

Thanks ! Could you make a ticket for this change to singular, please ? And building the doc is not yet something that could be tried with hope of success, I think. Maybe better after https://trac.sagemath.org/ticket/14153 Le lundi 7 août 2017 03:25:04 UTC+2, François Bissey a écrit : > > > >

Re: [sage-devel] python3 (not yet, and not for soon)

On Monday, August 7, 2017 at 1:25:04 PM UTC+12, François Bissey wrote: > > > > On 07/08/17 13:18, François Bissey wrote: > > On 05/08/17 23:56, Frédéric Chapoton wrote: > >> Could you please try with the branch "public/python3-experiment-v0" > >> that I have just put in trac. This is a (very

Re: [sage-devel] python3 (not yet, and not for soon)

On 07/08/17 13:18, François Bissey wrote: On 05/08/17 23:56, Frédéric Chapoton wrote: Could you please try with the branch "public/python3-experiment-v0" that I have just put in trac. This is a (very ugly) sequence of ad-hoc fix-up commits, just to see up to where we can go. That bit is

Re: [sage-devel] python3 (not yet, and not for soon)

On 05/08/17 23:56, Frédéric Chapoton wrote: Could you please try with the branch "public/python3-experiment-v0" that I have just put in trac. This is a (very ugly) sequence of ad-hoc fix-up commits, just to see up to where we can go. That bit is not python2 compatible: diff --git

Re: [sage-devel] python3 (not yet, and not for soon)

I’ll give it a go on Monday. > On 5/08/2017, at 23:56, Frédéric Chapoton wrote: > > Indeed. I should probably use "make build" and try again, but this takes so > long. I have installed gdb and got a longer log. > > I have met the issue that you report with Unknown. It

Re: [sage-devel] python3 (not yet, and not for soon)

Indeed. I should probably use "make build" and try again, but this takes so long. I have installed gdb and got a longer log. I have met the issue that you report with Unknown. It needs to be fixed, for sure. Could you please try with the branch "public/python3-experiment-v0" that I have just

Re: [sage-devel] python3 (not yet, and not for soon)

> On 5/08/2017, at 23:22, Frédéric Chapoton wrote: > > /home/chapoton/sage3/local/lib/libpython2.7.so.1.0(PyInt_FromLong+0x53)[0x7f950a139ef3] > /home/chapoton/sage3/local/lib/libpynac.so.13(+0x88196)[0x7f950a559196] > Pynac still being built and link to python 2.7 may

[sage-devel] python3 (not yet, and not for soon)

Dear all, we (should I say we ?) are making *slowly* progress towards python3. * The conversion of cmp to richcmp is underway. There remains about 35 files containing old-style cmp, that may be the hardest cases to handle. * One of the next steps would be to handle "div". There is