date:20230123

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread 'tsc...@ucdavis.edu' via sage-release

Thank you, that worked.

Best,
Travis


On Tuesday, January 24, 2023 at 11:28:48 AM UTC+9 matthia...@gmail.com 
wrote:

> ./configure --without-system-nauty 
>
> On Monday, January 23, 2023 at 4:30:05 PM UTC-8 tsc...@ucdavis.edu wrote:
>
>> Would it be better to just remove nauty or is there a way to force Sage 
>> to build and link with its own copy of nauty?
>>
>> Thanks,
>> Travis
>>
>>
>> On Monday, January 23, 2023 at 6:51:45 PM UTC+9 François Bissey wrote:
>>
>>> It is indeed a known issue with nauty on debian/ubuntu. That's the first 
>>> time someone mentioned it in a while but it is definitely broken. 
>>>
>>> On 23/01/23 21:28, Antonio Rojas wrote: 
>>> > 
>>> > 
>>> > El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
>>> > escribió: 
>>> > I am getting stuck at giac, even after a make distclean (I rebuilt 
>>> > 9.8.beta6 just to confirm this is a problem with the upgrade and 
>>> almost 
>>> > certainly due to #34857). Sorry for posting the log files; I can't 
>>> seem 
>>> > to include attachments... 
>>> > 
>>> > This is an underlinking issue in your distro's nauty package. Given 
>>> that 
>>> > upstream nauty doesn't build a shared library, it must be caused by 
>>> some 
>>> > incomplete distro custom patch. Try disabling system nauty. 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> > Groups "sage-release" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> > an email to sage-release...@googlegroups.com 
>>> > . 
>>> > To view this discussion on the web visit 
>>> > 
>>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com
>>>  
>>> <
>>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email_source=footer>.
>>>  
>>>
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/ce422786-79b3-4337-a94d-0e3c681cac0an%40googlegroups.com.

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread Matthias Köppe

./configure --without-system-nauty 

On Monday, January 23, 2023 at 4:30:05 PM UTC-8 tsc...@ucdavis.edu wrote:

> Would it be better to just remove nauty or is there a way to force Sage to 
> build and link with its own copy of nauty?
>
> Thanks,
> Travis
>
>
> On Monday, January 23, 2023 at 6:51:45 PM UTC+9 François Bissey wrote:
>
>> It is indeed a known issue with nauty on debian/ubuntu. That's the first 
>> time someone mentioned it in a while but it is definitely broken. 
>>
>> On 23/01/23 21:28, Antonio Rojas wrote: 
>> > 
>> > 
>> > El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
>> > escribió: 
>> > I am getting stuck at giac, even after a make distclean (I rebuilt 
>> > 9.8.beta6 just to confirm this is a problem with the upgrade and almost 
>> > certainly due to #34857). Sorry for posting the log files; I can't seem 
>> > to include attachments... 
>> > 
>> > This is an underlinking issue in your distro's nauty package. Given 
>> that 
>> > upstream nauty doesn't build a shared library, it must be caused by 
>> some 
>> > incomplete distro custom patch. Try disabling system nauty. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "sage-release" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to sage-release...@googlegroups.com 
>> > . 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com
>>  
>> <
>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email_source=footer>.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/5b9c8cd6-9d07-4487-9c42-e341eb601edfn%40googlegroups.com.

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread Matthias Köppe

./configure --without-system-libnauty 

On Monday, January 23, 2023 at 4:30:05 PM UTC-8 tsc...@ucdavis.edu wrote:

> Would it be better to just remove nauty or is there a way to force Sage to 
> build and link with its own copy of nauty?
>
> Thanks,
> Travis
>
>
> On Monday, January 23, 2023 at 6:51:45 PM UTC+9 François Bissey wrote:
>
>> It is indeed a known issue with nauty on debian/ubuntu. That's the first 
>> time someone mentioned it in a while but it is definitely broken. 
>>
>> On 23/01/23 21:28, Antonio Rojas wrote: 
>> > 
>> > 
>> > El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
>> > escribió: 
>> > I am getting stuck at giac, even after a make distclean (I rebuilt 
>> > 9.8.beta6 just to confirm this is a problem with the upgrade and almost 
>> > certainly due to #34857). Sorry for posting the log files; I can't seem 
>> > to include attachments... 
>> > 
>> > This is an underlinking issue in your distro's nauty package. Given 
>> that 
>> > upstream nauty doesn't build a shared library, it must be caused by 
>> some 
>> > incomplete distro custom patch. Try disabling system nauty. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "sage-release" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to sage-release...@googlegroups.com 
>> > . 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com
>>  
>> <
>> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email_source=footer>.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b83037ad-f662-4b06-b811-137dc4b07db4n%40googlegroups.com.

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread 'tsc...@ucdavis.edu' via sage-release

Would it be better to just remove nauty or is there a way to force Sage to 
build and link with its own copy of nauty?

Thanks,
Travis


On Monday, January 23, 2023 at 6:51:45 PM UTC+9 François Bissey wrote:

> It is indeed a known issue with nauty on debian/ubuntu. That's the first 
> time someone mentioned it in a while but it is definitely broken.
>
> On 23/01/23 21:28, Antonio Rojas wrote:
> > 
> > 
> > El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
> > escribió:
> > I am getting stuck at giac, even after a make distclean (I rebuilt 
> > 9.8.beta6 just to confirm this is a problem with the upgrade and almost 
> > certainly due to #34857). Sorry for posting the log files; I can't seem 
> > to include attachments...
> > 
> > This is an underlinking issue in your distro's nauty package. Given that 
> > upstream nauty doesn't build a shared library, it must be caused by some 
> > incomplete distro custom patch. Try disabling system nauty.
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to sage-release...@googlegroups.com 
> > .
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com
>  
> <
> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email_source=footer
> >.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6bf48137-7e9a-4f99-85f0-c3b309e109ebn%40googlegroups.com.

[sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread John H Palmieri

Could it be #34547, #16522, or #33842? I'm just taking guesses based on the 
newly merged tickets.

On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
wrote:

> From someone called mantepse in the sage-shell-mode 
> 
>  issue 
> on github :
>
> ```
> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
> use beta7 in the same emacs session.
> ```
>
> I don't get it either...
>
> There are two short Python files in the current `sahe-shell-mode` emacs 
> package, which are my prime suspects for an incompatibility with Python 
> 3.11. Now for a strategy for debugging *this*...
>
> Any idea ?
>
> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>
>> Emacs stopped working for me again!  I don't get it.
>>
>> This is terrible.
>>
>> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
>> wrote:
>>
>>> This patches fix my Fricas issue indeed. But losing the Emacs interface 
>>> is a big hit for me, so I revert to 9.6.beta6 for now.
>>>
>>> Thank you nevertheless !
>>>
>>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>>>
 In the hopes that this will fix it, I opened 
 https://trac.sagemath.org/ticket/34927.



 On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:

> Does this change fix the fricas.py failure?
>
> diff --git a/src/sage/interfaces/fricas.py 
> b/src/sage/interfaces/fricas.py
> index dc2ce71f26..ceba6f90dc 100644
> --- a/src/sage/interfaces/fricas.py
> +++ b/src/sage/interfaces/fricas.py
> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>  """
>  EXAMPLES::
>  
> -sage: fricas.__reduce__() 
>   # optional - fricas
> +sage: FriCAS().__reduce__()   
>   # optional - fricas
>  (, ())
>  sage: f, args = _ 
>   # optional - fricas
>  sage: f(*args) 
>
>
>
> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
> emanuel.c...@gmail.com wrote:
>
>> Apart from the  Emacs issye alteady reported 
>> , 
>> I get the three permanent failures I reported for the previous betas, as 
>> well as a new one, which gives three errors :
>>
>> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
>> 259.6 --random-seed=41414648133166628206443904124754495105 
>> src/sage/interfaces/fricas.py  # 3 doctests failed
>> Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
>> Git branch: develop
>> Git ref: 9.8.beta7
>> Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
>> SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
>> Using 
>> --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
>> Features to be detected: 
>> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
>> Doctesting 1 file.
>> sage -t --long --warn-long 259.6 
>> --random-seed=41414648133166628206443904124754495105 
>> src/sage/interfaces/fricas.py
>> **
>> File "src/sage/interfaces/fricas.py", line 894, in 
>> sage.interfaces.fricas.FriCAS.__reduce__
>> Failed example:
>> fricas.__reduce__()   # 
>> optional - fricas
>> Exception raised:
>>
>> Traceback (most recent call last):
>>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, 
>> in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, 
>> in compile_and_execute
>> exec(compiled, globs)
>>   File "", 
>> line 1, in 
>> fricas.__reduce__()   
>> # optional - fricas
>>   File "/usr/lib/python3.10/copyreg.py", line 76, in _reduce_ex
>>

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread Matthias Köppe

I've opened https://trac.sagemath.org/ticket/34932 for this

On Monday, January 23, 2023 at 1:51:45 AM UTC-8 François Bissey wrote:

> It is indeed a known issue with nauty on debian/ubuntu. That's the first 
> time someone mentioned it in a while but it is definitely broken.
>
> On 23/01/23 21:28, Antonio Rojas wrote:
> > 
> > 
> > El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
> > escribió:
> > I am getting stuck at giac, even after a make distclean (I rebuilt 
> > 9.8.beta6 just to confirm this is a problem with the upgrade and almost 
> > certainly due to #34857). Sorry for posting the log files; I can't seem 
> > to include attachments...
> > 
> > This is an underlinking issue in your distro's nauty package. Given that 
> > upstream nauty doesn't build a shared library, it must be caused by some 
> > incomplete distro custom patch. Try disabling system nauty.
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to sage-release...@googlegroups.com 
> > .
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com
>  
> <
> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email_source=footer
> >.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/46f2ea33-db59-4146-a168-087a7f754195n%40googlegroups.com.

[sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread Emmanuel Charpentier

>From someone called mantepse in the sage-shell-mode 
 
issue 
on github :

```
It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
use beta7 in the same emacs session.
```

I don't get it either...

There are two short Python files in the current `sahe-shell-mode` emacs 
package, which are my prime suspects for an incompatibility with Python 
3.11. Now for a strategy for debugging *this*...

Any idea ?

Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :

> Emacs stopped working for me again!  I don't get it.
>
> This is terrible.
>
> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com wrote:
>
>> This patches fix my Fricas issue indeed. But losing the Emacs interface 
>> is a big hit for me, so I revert to 9.6.beta6 for now.
>>
>> Thank you nevertheless !
>>
>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>>
>>> In the hopes that this will fix it, I opened 
>>> https://trac.sagemath.org/ticket/34927.
>>>
>>>
>>>
>>> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
>>>
 Does this change fix the fricas.py failure?

 diff --git a/src/sage/interfaces/fricas.py 
 b/src/sage/interfaces/fricas.py
 index dc2ce71f26..ceba6f90dc 100644
 --- a/src/sage/interfaces/fricas.py
 +++ b/src/sage/interfaces/fricas.py
 @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
  """
  EXAMPLES::
  
 -sage: fricas.__reduce__() 
   # optional - fricas
 +sage: FriCAS().__reduce__()   
   # optional - fricas
  (, ())
  sage: f, args = _ 
   # optional - fricas
  sage: f(*args) 



 On Friday, January 20, 2023 at 12:34:21 PM UTC-8 emanuel.c...@gmail.com 
 wrote:

> Apart from the  Emacs issye alteady reported 
> , 
> I get the three permanent failures I reported for the previous betas, as 
> well as a new one, which gives three errors :
>
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
> 259.6 --random-seed=41414648133166628206443904124754495105 
> src/sage/interfaces/fricas.py  # 3 doctests failed
> Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
> Git branch: develop
> Git ref: 9.8.beta7
> Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
> SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
> Using 
> --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
> Doctesting 1 file.
> sage -t --long --warn-long 259.6 
> --random-seed=41414648133166628206443904124754495105 
> src/sage/interfaces/fricas.py
> **
> File "src/sage/interfaces/fricas.py", line 894, in 
> sage.interfaces.fricas.FriCAS.__reduce__
> Failed example:
> fricas.__reduce__()   # 
> optional - fricas
> Exception raised:
>
> Traceback (most recent call last):
>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, 
> in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, 
> in compile_and_execute
> exec(compiled, globs)
>   File "", 
> line 1, in 
> fricas.__reduce__()   
> # optional - fricas
>   File "/usr/lib/python3.10/copyreg.py", line 76, in _reduce_ex
> raise TypeError(f"cannot pickle {cls.__name__!r} object")
> TypeError: cannot pickle 'LazyImport' object
> **
> File "src/sage/interfaces/fricas.py", line 896, in 
> sage.interfaces.fricas.FriCAS.__reduce__
>

Re: [sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread François Bissey

It is indeed a known issue with nauty on debian/ubuntu. That's the first 
time someone mentioned it in a while but it is definitely broken.


On 23/01/23 21:28, Antonio Rojas wrote:



El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
escribió:
I am getting stuck at giac, even after a make distclean (I rebuilt 
9.8.beta6 just to confirm this is a problem with the upgrade and almost 
certainly due to #34857). Sorry for posting the log files; I can't seem 
to include attachments...


This is an underlinking issue in your distro's nauty package. Given that 
upstream nauty doesn't build a shared library, it must be caused by some 
incomplete distro custom patch. Try disabling system nauty.


--
You received this message because you are subscribed to the Google 
Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to sage-release+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com .


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b390333d-6af3-bc05-99ba-2784319548c2%40gmail.com.

[sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread 'axio...@yahoo.de' via sage-release

Emacs stopped working for me again!  I don't get it.

This is terrible.

On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com wrote:

> This patches fix my Fricas issue indeed. But losing the Emacs interface is 
> a big hit for me, so I revert to 9.6.beta6 for now.
>
> Thank you nevertheless !
>
> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>
>> In the hopes that this will fix it, I opened 
>> https://trac.sagemath.org/ticket/34927.
>>
>>
>>
>> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
>>
>>> Does this change fix the fricas.py failure?
>>>
>>> diff --git a/src/sage/interfaces/fricas.py 
>>> b/src/sage/interfaces/fricas.py
>>> index dc2ce71f26..ceba6f90dc 100644
>>> --- a/src/sage/interfaces/fricas.py
>>> +++ b/src/sage/interfaces/fricas.py
>>> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>>>  """
>>>  EXAMPLES::
>>>  
>>> -sage: fricas.__reduce__()   
>>> # optional - fricas
>>> +sage: FriCAS().__reduce__() 
>>> # optional - fricas
>>>  (, ())
>>>  sage: f, args = _   
>>> # optional - fricas
>>>  sage: f(*args) 
>>>
>>>
>>>
>>> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 emanuel.c...@gmail.com 
>>> wrote:
>>>
 Apart from the  Emacs issye alteady reported 
 , 
 I get the three permanent failures I reported for the previous betas, as 
 well as a new one, which gives three errors :

 charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
 259.6 --random-seed=41414648133166628206443904124754495105 
 src/sage/interfaces/fricas.py  # 3 doctests failed
 Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
 Git branch: develop
 Git ref: 9.8.beta7
 Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
 SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
 Using 
 --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
 Features to be detected: 
 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
 Doctesting 1 file.
 sage -t --long --warn-long 259.6 
 --random-seed=41414648133166628206443904124754495105 
 src/sage/interfaces/fricas.py
 **
 File "src/sage/interfaces/fricas.py", line 894, in 
 sage.interfaces.fricas.FriCAS.__reduce__
 Failed example:
 fricas.__reduce__()   # 
 optional - fricas
 Exception raised:

 Traceback (most recent call last):
   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in 
 _run
 self.compile_and_execute(example, compiler, test.globs)
   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, 
 in compile_and_execute
 exec(compiled, globs)
   File "", 
 line 1, in 
 fricas.__reduce__()   # 
 optional - fricas
   File "/usr/lib/python3.10/copyreg.py", line 76, in _reduce_ex
 raise TypeError(f"cannot pickle {cls.__name__!r} object")
 TypeError: cannot pickle 'LazyImport' object
 **
 File "src/sage/interfaces/fricas.py", line 896, in 
 sage.interfaces.fricas.FriCAS.__reduce__
 Failed example:
 f, args = _   # 
 optional - fricas
 Exception raised:

 Traceback (most recent call last):
   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in 
 _run
 self.compile_and_execute(example, compiler, test.globs)
   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, 
 in compile_and_execute
 exec(compiled, globs)
   File "", 
 line 1, in 
 f, args = _   # 
 optional - fricas
 TypeError: cannot unpack non-iterable int object

[sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread Antonio Rojas



El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
escribió:
I am getting stuck at giac, even after a make distclean (I rebuilt 
9.8.beta6 just to confirm this is a problem with the upgrade and almost 
certainly due to #34857). Sorry for posting the log files; I can't seem to 
include attachments...

This is an underlinking issue in your distro's nauty package. Given that 
upstream nauty doesn't build a shared library, it must be caused by some 
incomplete distro custom patch. Try disabling system nauty.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com.

[sage-release] Re: Sage 9.8.beta7 released

2023-01-23 Thread 'tsc...@ucdavis.edu' via sage-release

I am getting stuck at giac, even after a make distclean (I rebuilt 
9.8.beta6 just to confirm this is a problem with the upgrade and almost 
certainly due to #34857). Sorry for posting the log files; I can't seem to 
include attachments...

[giac-1.9.0.15p0] /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `graph_free@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `clique_unweighted_find_single@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `graph_new@CLIQUER_1'
[giac-1.9.0.15p0] collect2: error: ld returned 1 exit status
[giac-1.9.0.15p0] make[7]: *** [Makefile:784: aide] Error 1
[giac-1.9.0.15p0] make[7]: *** Waiting for unfinished jobs
[giac-1.9.0.15p0] icas.o: in function `texmacs_graph_output(giac::gen 
const&, giac::gen&, std::__cxx11::basic_string, std::allocator >&, int, giac::context 
const*)':
[giac-1.9.0.15p0] 
/home/travis/sage-build/local/var/tmp/sage/build/giac-1.9.0.15p0/src/src/icas.cc:500:
 
warning: the use of `tmpnam' is dangerous, better use `mkstemp'
[giac-1.9.0.15p0] /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `graph_free@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `clique_unweighted_find_single@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
undefined reference to `graph_new@CLIQUER_1'
[giac-1.9.0.15p0] collect2: error: ld returned 1 exit status
[giac-1.9.0.15p0] make[7]: *** [Makefile:792: icas] Error 1
[giac-1.9.0.15p0] make[6]: *** [Makefile:507: all-recursive] Error 1
[giac-1.9.0.15p0] make[5]: *** [Makefile:437: all] Error 2
[giac-1.9.0.15p0] 
**
[giac-1.9.0.15p0] Error building giac-1.9.0.15p0
[giac-1.9.0.15p0] 
**

Let me know what specific log info would be useful.

Best,
Travis

On Sunday, January 22, 2023 at 10:41:04 PM UTC+9 emanuel.c...@gmail.com 
wrote:

> This patches fix my Fricas issue indeed. But losing the Emacs interface is 
> a big hit for me, so I revert to 9.6.beta6 for now.
>
> Thank you nevertheless !
>
> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>
>> In the hopes that this will fix it, I opened 
>> https://trac.sagemath.org/ticket/34927.
>>
>>
>>
>> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
>>
>>> Does this change fix the fricas.py failure?
>>>
>>> diff --git a/src/sage/interfaces/fricas.py 
>>> b/src/sage/interfaces/fricas.py
>>> index dc2ce71f26..ceba6f90dc 100644
>>> --- a/src/sage/interfaces/fricas.py
>>> +++ b/src/sage/interfaces/fricas.py
>>> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>>>  """
>>>  EXAMPLES::
>>>  
>>> -sage: fricas.__reduce__()   
>>> # optional - fricas
>>> +sage: FriCAS().__reduce__() 
>>> # optional - fricas
>>>  (, ())
>>>  sage: f, args = _   
>>> # optional - fricas
>>>  sage: f(*args) 
>>>
>>>
>>>
>>> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 emanuel.c...@gmail.com 
>>> wrote:
>>>
 Apart from the  Emacs issye alteady reported 
 , 
 I get the three permanent failures I reported for the previous betas, as 
 well as a new one, which gives three errors :

 charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
 259.6 --random-seed=41414648133166628206443904124754495105 
 src/sage/interfaces/fricas.py  # 3 doctests failed
 Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
 Git branch: develop
 Git ref: 9.8.beta7
 Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
 SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
 Using 
 --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
 Features to be detected:

Re: [sage-release] Re: Sage 9.8.beta7 released

Re: [sage-release] Re: Sage 9.8.beta7 released

Re: [sage-release] Re: Sage 9.8.beta7 released

Re: [sage-release] Re: Sage 9.8.beta7 released

[sage-release] Re: Sage 9.8.beta7 released

Re: [sage-release] Re: Sage 9.8.beta7 released

[sage-release] Re: Sage 9.8.beta7 released

Re: [sage-release] Re: Sage 9.8.beta7 released

[sage-release] Re: Sage 9.8.beta7 released

[sage-release] Re: Sage 9.8.beta7 released

[sage-release] Re: Sage 9.8.beta7 released

11 matches

Site Navigation

Mail list logo

Footer information