> First of all, you're really on your own as far as Python2 is concerned.
Yes, I know and understand this. The intention behind this was merely to
provide another data point, as Nils noticed.
> It's not clear from your message whether you saw any difference from
> python3 vs "sage --python".
Thanks, it’s this function and a similar one the other way, i.e. an FPyLLL
issue when used inside Sage:
```
cdef int assign_mpz(mpz_t& t, value) except -1:
"""
Assign Python integer to Z_NR[mpz_t]
"""
if isinstance(value, int) and PY_MAJOR_VERSION == 2:
mpz_set_si(t,
Of course going back to py2 is not a solution but the data point is
indicative that a regression was introduced, and that would be worth
solving. It looks to me the following code is what exhibits the problematic
behaviour. Run on a recent sage (9.7 or so):
sage: from fpylll import *
sage: FPLL
First of all, you're really on your own as far as Python2 is concerned.
We've moved on, there is no reason to use it on anything but
unupgradable old software.
It's not clear from your message whether you saw any difference from
python3 vs "sage --python".
Could you clarify?
Could you please also
P erroneously thinks that GA(1,5) is less than A5. I have no idea what's
causing that either.
On Wednesday, January 11, 2023 at 11:21:39 AM UTC-7 Trevor Karn wrote:
> Thanks for the confirmation. I'll double check this is not a logic bug
> before I open a ticket.
>
> On Wednesday, January 11,
Thanks for the confirmation. I'll double check this is not a logic bug
before I open a ticket.
On Wednesday, January 11, 2023 at 1:20:09 PM UTC-5 Trevor Karn wrote:
> At least part of the problem is that I gave bad generators for GA(1,5). It
> should be [[(1,2,3,4,5)],[(2,3,5,4)]].
>
> On Wedne
At least part of the problem is that I gave bad generators for GA(1,5). It
should be [[(1,2,3,4,5)],[(2,3,5,4)]].
On Wednesday, January 11, 2023 at 11:58:32 AM UTC-5 Trevor Karn wrote:
> Hi all,
>
> I was wondering if anyone can reproduce this bug with Poset creation. I
> create a Poset by pass
I confirm the error: P.maximal_elements() contains S5 and A5.
As a possibly minimal example, it suffices to use only the last 3 groups: I
also see the error with
P = Poset(data=(groups[16:], compare), element_labels=strs[16:]).
Please open a ticket.
On Wednesday, January 11, 2023 at 9:58:32 A
Hi all,
I was wondering if anyone can reproduce this bug with Poset creation. I
create a Poset by passing the elements and the comparison function as a
tuple (elements, func) and a pair of elements for which func(x,y) returns
True has P.lequal(x,y) returning False
I'm trying to create the subg
Hi all,
I am one of the persons Julian meant with “we”, thus able to clarify a bit
about the setup:
On our servers, where we noticed the problem first, we are running Ubuntu
with sagemath installed from their official repos. One server still had
sage 8.1 available, which is where we noticed the
On Wed, Jan 11, 2023 at 2:02 PM 'Julian Nowakowski' via sage-devel
wrote:
>
> Hi Dima,
>
> thank you for your suggestion.
>
> We still think that this issue is Sage-related.
> We have already tried to figure out, whether the slowdown is simply an issue
> of fpylll.
> If that was the case, then th
Hi Dima,
thank you for your suggestion.
We still think that this issue is Sage-related.
We have already tried to figure out, whether the slowdown is simply an
issue of fpylll.
If that was the case, then the slowdown would probably be caused by one of
the following two issues:
1) The newer vers
A part of SageTeX is sensitive to LaTeX representations of Sage
objects - one of the macros requires that it's not split into several
paragraphs.
This was reported on https://github.com/sagemath/sagetex/issues/64
In this case it turned out that tikz represention of polyhedra are to
blame - easily
13 matches
Mail list logo
