>
>
>
> I don't yet have a blog but will create one soon. I will post a link here
> when it is up and will use it to document the project progress. My Sage
> experience so far has mostly been with the arithmetic dynamics
> functionality and progress in that area is managed within a page of the
Firefox on Windows 10. Firefox on OS X El Capitan has the same problem.
Chrome and Safari on OS X are both functional.
On Monday, May 2, 2016 at 7:37:43 PM UTC-7, Andrey Novoseltsev wrote:
>
> Which browser OS are you using? I just checked now and have the same
> issue with Firefox on Windows. C
Which browser OS are you using? I just checked now and have the same
issue with Firefox on Windows. Chrome on Windows seems to work (I even
have working 3d plot with JSmol, which is a bit unexpected!).
Yesterday both Firefox and Chrome worked under Linux.
Regarding changes - I was using develop br
Andrey, the test server is not completing evaluations. Just get the
spinning GIF.
Also, I'm curious as to why you're making modifications in the master
branch of the sagecell repository. I happened to be reading the JavaScript
source code right when you split it into smaller files yesterday, an
Thanks! I really appreciate you taking the time to mentor this project!
I don't yet have a blog but will create one soon. I will post a link here
when it is up and will use it to document the project progress. My Sage
experience so far has mostly been with the arithmetic dynamics
functionality
Welcome to the Sage community, Arpit! I'm sure this GSoC project will
become a very nice addition to Sage :-)
Best,
Johan
--
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 em
Welcome!
Now we have a couple of weeks for "community bonding" before you actually
start working in the project. I guess that means this is the time where you
get used to Sage development workflow: the trac server, review process,
discussions in this mailing lists and so on. Since you have alre
Thanks for sharing this Victor. It looks like there are some additional
really good speedups there.
Flint has always had just reasonable matrix code, nothing extraordinary.
I put quite a bit of work into the recent minpoly and charpoly code I put
into Flint (which NTL was already very good at).
On Monday, May 2, 2016, Michael Orlitzky wrote:
> On 05/02/2016 06:07 AM, Erik Bray wrote:
> > On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer > wrote:
> >> My vote:
> >>
> >>> [X] Phase out properties which perform any non-trivial computation
> >>
> >>
> >> In certain cases, properties might be
On 05/02/2016 06:07 AM, Erik Bray wrote:
> On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer
> wrote:
>> My vote:
>>
>>> [X] Phase out properties which perform any non-trivial computation
>>
>>
>> In certain cases, properties might be useful (but it could very well be that
>> there are 0 such cases
> Consistency is a definitive plus, as well as not impeding
> introspection. So I would tend to agree to officially phase out
> properties from the public API.
>
> There is one use case for properties in the public API though which I
> would like to bring up, namely "glorified methods".
> ...
Yes,
As the author of #20182, I don't think that the behavior of `sage -t`
changed. #20182 triggers a new behavior only if you put
"optional=...,external,..." in the argument list. On the other hand, new
definitions of
make (p)testoptional(long)
make (p)testall(long)
indeed include "optional=sage,o
Hi all,
Since February this year, Alex Best has been working for us in
Kaiserslautern on a new superoptimiser for assembly language in MPIR. The
superoptimiser is now working beautifully, but Alex has managed to get
himself a PhD position and will be leaving us at the end of July this year.
Th
On Mon, May 2, 2016 at 2:52 PM, Erik Bray wrote:
> On Wed, Apr 27, 2016 at 5:05 PM, William Stein wrote:
>> On Wed, Apr 27, 2016 at 7:09 AM, Kwankyu Lee wrote:
>>> This discussion is hardening the terms: Sage core and external packages. But
>>> from the point of view of the people developing the
On Wed, Apr 27, 2016 at 5:05 PM, William Stein wrote:
> On Wed, Apr 27, 2016 at 7:09 AM, Kwankyu Lee wrote:
>> This discussion is hardening the terms: Sage core and external packages. But
>> from the point of view of the people developing the would-be external
>> packages, the official term would
On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer wrote:
> My vote:
>
>> [X] Phase out properties which perform any non-trivial computation
>
>
> In certain cases, properties might be useful (but it could very well be that
> there are 0 such cases in Sage).
I generally feel that properties *should*
On 2016-04-29 10:38, Nicolas M. Thiery wrote:
P.f(x) # use the morphism as a function
P.f.rank() # play with the morphism itself
cached method also does this.
You can do P.f(x) to call the cached_method f but you also do stuff like
P.f.clear_cach
Hi everyone,
I am one of the students selected to work on Sage this summer for GSoC 2016
and just wanted to introduce myself and my project here. Currently I am a
pure math graduate student at Florida State University and am interested in
algebraic geometry. The goal of the GSoC project I will
My vote:
[X] Phase out properties which perform any non-trivial computation
In certain cases, properties might be useful (but it could very well be
that there are 0 such cases in Sage).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsu
19 matches
Mail list logo
