OK, embedding seems to work for Chrome and Firefox, so reported
regressions are fixed.
I am planning to switch main servers in 3 weeks. (Probably 7.2 will be
out by then, so I'll also see how easy it is to upgrade with the new
setup.)
--
You received this message because you are subscribed to th
The sagecell repository accepts pull requests.
--
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 post to this group, sen
Made it work in Chrome via
https://github.com/sagemath/sagecell/commit/95d2b406026ea7efc73a91ef693a1dd9fb5946c6
(my attempts to create all wrappers using a loop were not successful)
Made some progress on CORS but there are still issues.
On Mon, Apr 25, 2016 at 2:35 AM, Volker Braun wrote:
> sage
This ticket may be relevant: http://trac.sagemath.org/ticket/13093
On Sun, May 1, 2016 at 9:57 AM, Hao Chen wrote:
> Hi, this might be stupid, but I was wondering if integrating a newform
> against an arbitrary Manin symbol
> is implemented in Sage now? I have in mind something like
>
> sage: m =
Hi, this might be stupid, but I was wondering if integrating a newform
against an arbitrary Manin symbol
is implemented in Sage now? I have in mind something like
sage: m = ModularSymbols(Gamma1(11),2).cuspidal_submodule().basis()[0]
sage: Newforms(11,2)[0].period(m) # ouput some complex number
Seems like you have a shell that errors on unset variables (or any posix
shell after running "set -u")
We should just get rid of this vestige now that we don't use
LD_LIBRARY_PATH any more...
I made. http://trac.sagemath.org/ticket/20529 for that.
On Sunday, May 1, 2016 at 6:12:59 PM UTC+2, F
Hello,
runing the patchbot 2.5.6 on sage 7.2.b6 on a new machine, I got failures
related to SAGE_ORIG_LD_LIBRARY_PATH, see part of the log below. Could this
be
related to the fact that the machine's default shell is not bash ?
Does anybody have an idea where this could come from ?
Frederic
sa
The best solution would probably be if the patchbot config file had a way
to exclude #optional stuff...
On Sunday, May 1, 2016 at 6:18:24 AM UTC+2, vdelecroix wrote:
>
> Hello,
>
> The ticket #20182 (merged 7.2.beta6) introduced a different behavior for
> `sage -t`. Namely it tests all availab
