This problem is also seen in the python3 patchbot report, as can be found
here :
https://patchbot.sagemath.org/log/0/Ubuntu/16.04/x86_64/4.4.0-141-generic/atlas/2019-02-24%2011:31:45?short
Frederic
Le mardi 26 février 2019 17:52:39 UTC+1, John Cremona a écrit :
>
> I am testing a new version
Hi Jeroen,
On 2019-02-27, Jeroen Demeyer wrote:
> By the way, why is it an issue in the first place? Is there any reason
> why you don't want to inherit from ModuleElement?
I don't know what Kwankyu has in mind, but conceivably it is possible to
have a parent that, depending on input
On 2019-02-26 23:44, Kwankyu Lee wrote:
It could be possible to hammer the coercion model to behave more nicely
with the category framework, at least with respect to the issue that I
raised.
By the way, why is it an issue in the first place? Is there any reason
why you don't want to inherit
Thanks. I agree that the obvious solution. Samuel Lelièvre has supplied
the patch and, for completeness, I have checked that it fixes the issue by
recompiling and given a positive review.
Andrew
On Tuesday, 26 February 2019 23:08:07 UTC+11, E. Madison Bray wrote:
>
> Hi Andrew,
>
> On Tue,
Hi Sebastian,
No, that is not a known bug. The issue comes from the fact that the
"Cartan" type ['H',3] is relabeled and relabeled Cartan types do not know
they should just relabel the underlying Coxeter diagram. This is now
https://trac.sagemath.org/ticket/27371.
Best,
Travis
On
Unicode has superscripts btw, would be neat to make use of that:
x⁴⁵⁶⁷⁸⁹
16 = 2⁴
>
--
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
Hi,
is the following a known bug?
sage: RH3 = ReflectionGroup(['H', 3])
sage: RH3.coxeter_matrix()
Traceback (most recent call last):
...
TypeError: 'NotImplementedType' object is not callable
This already occurs on stable 8.5 but still was working on 8.1:
sage: RH3.coxeter_matrix()
[1 3 2]
On Wednesday, February 27, 2019 at 7:06:42 AM UTC+9, Jeroen Demeyer wrote:
>
> On 2019-02-26 21:53, Jeroen Demeyer wrote:
> > I think that you are 100% right but that (as with many things) it is the
> > way it is for historical reasons and it hasn't bothered anyone
> > sufficiently much to
On 2019-02-26 21:53, Jeroen Demeyer wrote:
I think that you are 100% right but that (as with many things) it is the
way it is for historical reasons and it hasn't bothered anyone
sufficiently much to change it.
Part of the reason why I haven't personally touched _lmul_/_rmul_ (while
I did
On 2019-02-26 14:44, Kwankyu Lee wrote:
My question is: why should I use `ModuleElement` instead of just `Element`?
If I use `Element`, the scalar multiplication is not detected by the
coercion system. So I am forced to use `ModuleElement`.
Since my parent is in the category of modules over
On Tuesday, February 26, 2019 at 6:16:56 AM UTC-8, E. Madison Bray wrote:
>
> I'll note also that there is a 7 year old(!) open ticket about this
> at: https://trac.sagemath.org/ticket/13071
>
> I think it would be a very good problem to solve (maybe a GSoC student
> could do it?)
>
> ISTM
Hi Kwankyu,
On 2019-02-26, Kwankyu Lee wrote:
> Since my parent is in the category of modules over QQ, then I think
> elements of the parent should be automatically treated as module elements,
> and using `Element` should just be ok.
>
> What do you think?
I think that speed matters. I see
I am testing a new version of the standard spkg eclib, see
https://trac.sagemath.org/ticket/27360. I am getting doctesting failures
caused *only* because of changes in output buffering resulting in the tail
end of the output of one command appearing at the beginning of the output
of the next.
On Mon, Feb 11, 2019 at 6:07 PM Randall wrote:
>
> A couple of comments relating to my attempts to build Sage 8.6 on openSuse
> Leap 15.0 system. (64 bit Intel Core X980s)
>
> 1. The fplll build failed due to non-shareable segments in the libqd file,
> but I had to reinstall the libqd and libqd
I'll note also that there is a 7 year old(!) open ticket about this
at: https://trac.sagemath.org/ticket/13071
I think it would be a very good problem to solve (maybe a GSoC student
could do it?)
ISTM this should be possible by, given a symbolic expression, going
through it and renaming any
On Sun, Feb 24, 2019 at 8:38 AM Frédéric Chapoton wrote:
>
> Hello,
>
> Can someone having the required superpowers please close the 61
> duplicate/invalid/wonfix tickets that have a positive review on trac ?
Okay. At least for the ones that have positive_review I'll trust that
whoever set
On Mon, Feb 25, 2019 at 2:40 PM Sho wrote:
>
> Hi I'm getting the following error when trying to install sage from conda
>
> PackagesNotFoundError: The following packages are not available from current
> channels:
>
> - sage -> sagemath-db-conway-polynomials[version='>=0.5.*']
>
> Current
Hi,
I am defining a parent and elements in the category of modules over QQ. The
proper way would be to use the category framework:
from sage.structure.parent import Parent
from sage.structure.element import ModuleElement
from sage.categories.modules import Modules
class
On Tue, Feb 26, 2019 at 1:28 PM Jori Mäntysalo (TAU)
wrote:
>
> Is this a known feature?
>
> ...~/sage$ ./sage -c 'set_random_seed(0); print(randint(1, 10^6))'
> 111440
>
> ...~/sage3$ ./sage -c 'set_random_seed(0); print(randint(1, 10^6))'
> 116853
I wouldn't call it a "feature", but it is a
Is this a known feature?
...~/sage$ ./sage -c 'set_random_seed(0); print(randint(1, 10^6))'
111440
...~/sage3$ ./sage -c 'set_random_seed(0); print(randint(1, 10^6))'
116853
--
Jori Mäntysalo
Tampereen yliopisto - Ihminen ratkaisee
--
You received this message because you are subscribed to
Hi Andrew,
On Tue, Feb 26, 2019 at 12:31 AM Andrew wrote:
>
> Thanks very much for this Erik! It's the height of the grant writing season
> in the antipodeans so I have only just gotten back to this but you told how
> to troubleshoot and hence fix my problem, which turned out to be annoyingly
21 matches
Mail list logo
