The symbolic power of a matrix was requested and discussed in
Ask Sage question 25658 [0], and implemented in #22523 [1]. It now
works in basic cases (diagonalizable case, two by two case, ...).
As reported in Ask Sage question 41622 [2] though, it fails in some cases.
Ticket #25082 [3] implemen
On 2018-04-05 19:59, Simon King wrote:
But couldn't the same happen when putting $(SAGERUNTIME) into the list
of dependencies?
Of course. I never claimed to have a solution for the meataxe problem. I
am only identifying and explaining the problem.
--
You received this message because you are
Dear Jeroen,
On 2018-04-05, Jeroen Demeyer wrote:
> On 2018-04-05 17:53, Simon King wrote:
>> for the problem at #18514 it
>> would be fine to have `sage -b` *before* building p_group_cohomology.
>
> I'm not entirely sure which "problem at #18514" you are talking about,
> but that won't fix the
On 2018-04-05 17:53, Simon King wrote:
for the problem at #18514 it
would be fine to have `sage -b` *before* building p_group_cohomology.
I'm not entirely sure which "problem at #18514" you are talking about,
but that won't fix the "ImportError: No module named meataxe" problem.
Imagine that
On 2018-04-05 17:55, Simon King wrote:
And if both are supported: What are the differences?
Both "sagelib" and "$(SAGERUNTIME)" are supported.
The difference is that "sagelib" does not contain run-time dependencies
of Sage. For example, running Sage requires pexpect, so pexpect is part
of $(
Le mercredi 4 avril 2018 18:13:50 UTC+2, Dima Pasechnik a écrit :
>
> Could you post your patch here?
> It might be useful...
--
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
PS:
On 2018-04-05, Jeroen Demeyer wrote:
>> Suggested syntax: Including `sagelib` into the list of dependencies
>> of a package should trigger `sage -b` before installation.
>
> That is already supported. The problem is that you want *after*, not
> *before*.
Do you mean the exact syntax that I
Hi Jeroen,
On 2018-04-05, Jeroen Demeyer wrote:
>> Suggested syntax: Including `sagelib` into the list of dependencies
>> of a package should trigger `sage -b` before installation.
>
> That is already supported. The problem is that you want *after*, not
> *before*.
It depends on what spkg we ar
On 2018-04-05 12:57, Simon King wrote:
If it is ok that an optional package directly does `sage -b`
No, that is not OK. When you do that, you will spawn an independent
build of the Sage library. This happens while "make" is still running,
so "make" might also be building the Sage library at t
Sounds reasonable to me. Can you open a trac ticket for this?
On 28 March 2018 at 18:01, Nicolás Sirolli wrote:
> The Gauss sum for the Dirichlet character modulo 1 is equal to 1, but:
>
> sage: G = DirichletGroup(1)
> sage: chi = G.list()[0]
> sage: chi.gauss_sum()
> 0
>
> The output is zero be
Hi Dima,
On 2018-04-05, Dima Pasechnik wrote:
> On Thursday, April 5, 2018 at 11:06:26 AM UTC+2, Simon King wrote:
>> So, question: Do I need to manually change the permissions of scripts
>> generated by autotools in my spkg?
>>
>
> This looks strange to me. Where are the sources of the spkg in
On Thursday, April 5, 2018 at 11:06:26 AM UTC+2, Simon King wrote:
>
> Hi!
>
> Related with #18514 (Upgrade of group cohomology spkg), two or three
> questions came up:
>
> One part of the spkg is an autotoolised library. Autotools generates
> some install.sh script, whose permission do not i
Hi!
Related with #18514 (Upgrade of group cohomology spkg), two or three
questions came up:
One part of the spkg is an autotoolised library. Autotools generates
some install.sh script, whose permission do not include execution.
Nonetheless on my machine the package installs fine, whereas John
Pal
13 matches
Mail list logo
