[sage-devel] Re: Coexistence of py2 and py3

2019-09-24 Thread Simon King
Hi Dima, On 2019-09-24, Dima Pasechnik wrote: > I'm surprised that *.c files created by Cython for pyX may be used for > py(5-X) without many problems. > I'd expect this to break down totally... Indeed. It is surprising that I only got two kinds of spurious errors: In one place, a pickle of a di

Re: [sage-devel] Re: Coexistence of py2 and py3

2019-09-24 Thread Dima Pasechnik
I'm surprised that *.c files created by Cython for pyX may be used for py(5-X) without many problems. I'd expect this to break down totally... Dima On Tue, Sep 24, 2019 at 6:06 PM Simon King wrote: > > Hi Dima, > > On 2019-09-24, Dima Pasechnik wrote: > > Shouldn't coexisting installations like

[sage-devel] Re: Coexistence of py2 and py3

2019-09-24 Thread Simon King
Hi Dima, On 2019-09-24, Dima Pasechnik wrote: > Shouldn't coexisting installations like this have different --prefix ? Of course. But if I understand correctly, this only affects where stuff is installed, not where it is built. The situation is as follows: - the .c files are created in the sour

[sage-devel] Re: Coexistence of py2 and py3

2019-09-24 Thread Simon King
Hi Vincent, On 2019-09-24, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Are you sure that the problem comes from the C files? If you erase > them between the two installations what do you get? That's what I'm testing now. BTW, meanwhile I found that I can prescribe in my setup.py where