2014-09-28 21:01 UTC+02:00, mmarco :
> Typically invariants are polynomials with integer coefficients (sometimes
> with negative or even rational exponents). I guess they could be converted
> to a dictionary (maybe represented by a list), but doesn't sound like the
> kind of data structure that fit
Typically invariants are polynomials with integer coefficients (sometimes
with negative or even rational exponents). I guess they could be converted
to a dictionary (maybe represented by a list), but doesn't sound like the
kind of data structure that fits well on a databse index.
Maybe storing
Hi,
I finally made the Sage Days 6 [1] (Bristol, UK) videos available:
http://wiki.sagemath.org/days6/videos
Some are amusing, especially the developer interviews that Ondrej
Certik ran around doing...
[1] http://wiki.sagemath.org/days6
-- William
--
William Stein
Professor of Mathemati
On Saturday, September 27, 2014 10:36:14 PM UTC+2, kcrisman wrote:
>
> If I recall correctly sometimes one needs to use dash instead of bash on
> Cygwin, but nonetheless it somehow works, maybe because dash is only
> necessary when going "outside" of Sage for rebasing or something?
>
Yes, (appr
We do use the milestone to indicate duplicate/invalid/wontfix, at least.
Though I agree that we don't really need to update the milestone, if its
pointing at an older version then so what? Is anybody making trac queries
for specific milestones? If you want to know which tickets were closed then
On Sep 26, 2014, at 6:33 AM, kcrisman wrote:
>
> > After clicking Lastmod-header it got tickets sorted like
> >
> > 1 mins < 23 hours < 32 mins < 8 days
>
> It's not a direct answer to your question, but you might be interested
> in http://trac.sagemath.org/report/92
>
>
> This is nearl
On Sunday, September 28, 2014 1:00:42 AM UTC+2, rjf wrote:
>
>
>
> On Saturday, September 27, 2014 1:21:28 PM UTC-7, Volker Braun wrote:
>>
>> I guess you are really happy about python3, then.
>>
>> $ python3
>> Python 3.4.1 (default, Sep 7 2014, 11:02:45)
>> [GCC 4.9.1 20140813 (Red Hat 4.9.1-7)
On Sunday, September 28, 2014 12:00:42 AM UTC+1, rjf wrote:
>
> >>> 1/2
>> 0.5
>>
> I don't know what other new features it might have, but this one, it
> seems, would
> also interfere with Sage. Why can't it just be 1/2 ?
>
Because, like most real-world programming languages (or, for that mat
> This is nearly useless, though, except for tickets modified since the last
> Sage (official) release. Is there any way to get back to the "old" system
> where the milestone would change *without* changing the ticket - and hence
> the ticket last-mod time? It is very misleading to see ticket #xy
On 2014-09-26 14:50, kcrisman wrote:
I wish I could! I recall that Jeroen had to always ask someone else to
change the milestone, even he didn't have access to it as release
manager :)
Nobody ever told me how it was done, but I assume it was indeed a direct
manipulation of the Trac database.
10 matches
Mail list logo