Yes, SIGSEGV would be a problem, so I apologize if my responses are noise, 
but my impression is that the term "SIGSEGV" should not have been used.  
>From reading the text of the post that you replied to, it appears to me 
that the complaint was about "an incorrectly segmented return", which, from 
the examples, I interpreted to be a complaint about erroneous commas.  
Sorry if I'm off base.

On Sunday, August 15, 2021 at 12:32:52 PM UTC-6 dim...@gmail.com wrote:

>
>
> On Sun, 15 Aug 2021, 21:13 dmo...@deductivepress.ca, <
> dmo...@deductivepress.ca> wrote:
>
>> I don't think there is any problem -- the output is correct.  (And the 
>> original message seems to have been deleted.)  
>>
>
> SIGSEGV certainly is a problem.
>
> It is just that python prints an extra comma at the end of tuples of 
>> length 1, in order to make it clear that the parentheses represent a 
>> tuple.  For example:
>> sage: 
>> tuple([tuple([tuple([0])])])                                                 
>>                       
>>  
>> (((0,),),)
>>
>> On Sunday, August 15, 2021 at 3:55:03 AM UTC-6 dim...@gmail.com wrote:
>>
>>> How do you run Sage?
>>> What version, what OS?
>>> How is Sage installed?
>>>
>>>
>>> On Sun, 15 Aug 2021, 12:16 Leww, <bodn...@gmail.com> wrote:
>>>
>>>> Using nauty where the result has a singleton anywhere in the result 
>>>> gives an incorrectly segmented return. Below are some examples
>>>>
>>>> 1 possible construction:
>>>> sage: tuple(hypergraphs.nauty(2, 3, uniform=2))
>>>> (((0, 1), (0, 2)),)
>>>>
>>>> 1 edge
>>>> sage: tuple(hypergraphs.nauty(1, 2, uniform=2))
>>>> (((0, 1),),)
>>>>
>>>> 1 uniform case
>>>> sage: tuple(hypergraphs.nauty(2, 2, uniform=1))
>>>> (((0,), (1,)),)
>>>>
>>>> everything together
>>>> sage: tuple(hypergraphs.nauty(1, 1, uniform=1))
>>>> (((0,),),)
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "sage-devel" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to sage-devel+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/sage-devel/137e937a-fd98-4429-b9ca-2e206884e9c6n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/sage-devel/137e937a-fd98-4429-b9ca-2e206884e9c6n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/61d05705-5838-454c-9939-edbfc31ef999n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/61d05705-5838-454c-9939-edbfc31ef999n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8ee791ae-f308-4242-9394-216363f9d922n%40googlegroups.com.

Reply via email to