On Mon, Aug 16, 2021 at 9:14 AM Leww wrote:
>
> Sorry for the confusion, I made the post assuming that it came from the oddly
> formatted singleton tuples (now I know why there is an extra comma there).
> Later I found out that the error was caused by something else; since this
> thread is not d
Sorry for the confusion, I made the post assuming that it came from the
oddly formatted singleton tuples (now I know why there is an extra comma
there).
Later I found out that the error was caused by something else; since this
thread is not deleted here is the true source of the unhandled error
I certainly can't reproduce a SIGSEGV (i.e. a signal for memory access
violation).
So this is probably a badly formulated subject.
On Sun, Aug 15, 2021 at 9:11 PM dmo...@deductivepress.ca
wrote:
>
> Yes, SIGSEGV would be a problem, so I apologize if my responses are noise,
> but my impression is
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
On Sun, 15 Aug 2021, 21:13 dmo...@deductivepress.ca, <
dmor...@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
I don't think there is any problem -- the output is correct. (And the
original message seems to have been deleted.) 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
How do you run Sage?
What version, what OS?
How is Sage installed?
On Sun, 15 Aug 2021, 12:16 Leww, 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(hypergraph
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 u
