Thank you for the pointer for how to add the optional marker. Adding a
dummy spkg for when the Python version is sufficiently large feels like a
much more invasive hack around by going into the build system. ;)
Jonathan, yes, that is how we can fix the code. The problem as I recall is
the docte
On Friday, May 14, 2021 at 12:23:49 PM UTC-7 vdelecroix wrote:
> 1. sage-9.3 claims that it supports Python 3.6. My system Python
> was by the way accepted by sage configure script.
It did also warn you that using system python 3.6 is deprecated.
> 2. the part of sage source code that I ment
Its the same code in the Main line. Sorry for the confusion.
I googled it and that is how I found the exact place where this is defined.
What I linked is how it looks now accounting for changes in gmp 6.2. Flint
2.6.3 has it but not 2.5.2.On May 14, 2021 10:31 PM, Dima Pasechnik
wrote:
>
> On
On Fri, May 14, 2021 at 4:03 PM 'jonatha...@googlemail.com' via
sage-devel wrote:
>
> I think I tracked it down.
>
> https://github.com/BrianGladman/flint/blob/trunk/gmpcompat.h
this is a fork, dealing with Windows support of Flint.
We should be working with
https://github.com/wbhart/flint2
whic
On Fri, May 14, 2021 at 8:23 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> 1. sage-9.3 claims that it supports Python 3.6. My system Python
> was by the way accepted by sage configure script.
>
> 2. the part of sage source code that I mentioned in my initial e-mail
> does not
Thanks Freddie for reporting this.
I'm glad it resolves so easily. Yes, that is a mistake in our 9.2
configure. One can fix this by passing `--with-system-gmp=no` to
configure, but it should have rejected gmp 6.2 as long as flint 2.5.2 is
the install candidate.
So you can update sage or rebu
Awesome, many thanks for running this down.
`sage --standard | grep gmp`
>> gmp.6.1.2 (not_installed)
`equery --quiet list gmp`
>> dev-libs/gmp-6.2.1-r1
`sage --standard | grep flint`
>> flint...2.5.2.p5 (2.5.2.p5)
So yes, that
1. sage-9.3 claims that it supports Python 3.6. My system Python
was by the way accepted by sage configure script.
2. the part of sage source code that I mentioned in my initial e-mail
does not support Python 3.6
Hence this is a bug. Did I miss something?
Le 14/05/2021 à 20:21, Dima Pasec
we are dropping Python 3.6, it will reach eol in Dec.
On Fri, 14 May 2021, 18:43 Vincent Delecroix, <20100.delecr...@gmail.com>
wrote:
> Indeed, the method reconfigure was introduced in Python 3.7 (and I do
> have Python 3.6 on my system). The proper way to go is to use the
> codecs library.
>
>
Indeed, the method reconfigure was introduced in Python 3.7 (and I do
have Python 3.6 on my system). The proper way to go is to use the
codecs library.
Vincent
Le 14/05/2021 à 19:19, Vincent Delecroix a écrit :
Dear all,
On sage 9.3 and buckygen installed I got a lot of test failures
in graphs
I can at least confirm that
- sqlite3 shell is not installed on my system
quasar:~$ sqlite3
Command 'sqlite3' not found, but can be installed with:
apt install sqlite3
Please ask your administrator.
- Python sqlite3 library is
$ python3 -c 'import sqlite3; print(sqlite3.version)'
2.6.0
Vinc
Dear all,
On sage 9.3 and buckygen installed I got a lot of test failures
in graphs/graph_generators.py of the type
sage -t --long --random-seed=0 src/sage/graphs/graph_generators.py
**
File "src/sage/graphs/graph_generators.py"
I think I tracked it down.
https://github.com/BrianGladman/flint/blob/trunk/gmpcompat.h
In there you see that `flint_mpz_set_si` is modified to work with GMP 6.2
I'm assuming this one is picked up from your system?
`sage --standard | grep gmp`
This code is not present yet in flint 2.5.2, which
Thanks. Indeed, libffi is alive and well:
...
checking for ffi_closure_alloc in -lffi... yes
checking ffi/ffi.h usability... no
checking ffi/ffi.h presence... no
checking for ffi/ffi.h... no
checking ffi.h usability... yes
checking ffi.h presence... yes
checking for ffi.h... yes
checking whether w
On Fri, May 14, 2021 at 1:20 PM Michael Orlitzky wrote:
>
> On Fri, 2021-05-14 at 12:12 +0100, Dima Pasechnik wrote:
> > >
> > > The other possibility is that the linker is told not to look for
> > > system-wide libffi - can this be achieved with -L and -Wl,-rpath ?
> > >
> > > On the other hand,
On Fri, 2021-05-14 at 12:12 +0100, Dima Pasechnik wrote:
> >
> > The other possibility is that the linker is told not to look for
> > system-wide libffi - can this be achieved with -L and -Wl,-rpath ?
> >
> > On the other hand, it's a bug in maxima, which does not try to check
> > for presense of
On Fri, May 14, 2021 at 12:17 PM Jan Groenewald wrote:
>
> Hi
>
> On Fri, 14 May 2021 at 13:12, Dima Pasechnik wrote:
>>
>> On Fri, May 14, 2021 at 11:53 AM Dima Pasechnik wrote:
>> >
>> > On Fri, May 14, 2021 at 11:21 AM Jan Groenewald wrote:
>> > >
>> > > Hi
>> > >
>> > > On Fri, 14 May 2021
Hi
On Fri, 14 May 2021 at 13:12, Dima Pasechnik wrote:
> On Fri, May 14, 2021 at 11:53 AM Dima Pasechnik wrote:
> >
> > On Fri, May 14, 2021 at 11:21 AM Jan Groenewald wrote:
> > >
> > > Hi
> > >
> > > On Fri, 14 May 2021 at 11:26, François Bissey
> wrote:
> > >>
> > >> It looks like maxima.f
On Fri, May 14, 2021 at 11:53 AM Dima Pasechnik wrote:
>
> On Fri, May 14, 2021 at 11:21 AM Jan Groenewald wrote:
> >
> > Hi
> >
> > On Fri, 14 May 2021 at 11:26, François Bissey wrote:
> >>
> >> It looks like maxima.fas has not been built. Last time I saw that happen
> >> in sage-on-gentoo was
On Fri, May 14, 2021 at 11:21 AM Jan Groenewald wrote:
>
> Hi
>
> On Fri, 14 May 2021 at 11:26, François Bissey wrote:
>>
>> It looks like maxima.fas has not been built. Last time I saw that happen
>> in sage-on-gentoo was because the patch to build it was missing.
>> Not sure how it could happen
Hi
On Fri, 14 May 2021 at 11:26, François Bissey wrote:
> It looks like maxima.fas has not been built. Last time I saw that happen
> in sage-on-gentoo was because the patch to build it was missing.
> Not sure how it could happen on your setup, the log needs further
> inspection.
>
> > On 14/05/2
On Fri, May 14, 2021 at 10:19 AM John Cremona wrote:
>
> I have been installing sage-9.3 from the tarball on a few ubuntu
> machines, just doing ./configure and then make. On one machine
> running ubuntu 20.04.02 LTS maxima fails to build. I have attached
> the log files.
>
> This is a machine o
It looks like maxima.fas has not been built. Last time I saw that happen
in sage-on-gentoo was because the patch to build it was missing.
Not sure how it could happen on your setup, the log needs further inspection.
> On 14/05/2021, at 21:18, John Cremona wrote:
>
> I have been installing sage-9
23 matches
Mail list logo
