On Friday, January 10, 2014 6:30:12 AM UTC-10, Jeroen Demeyer wrote:
>
> I thought the policy was to *never* remove old pickles?
>
http://www.sagemath.org/doc/developer/coding_basics.html#the-pickle-jar
says:
Warning Sage’s pickle jar helps to ensure backward compatibility in sage.
Pickles sh
In practice Python is one of the non-specialist-maths parts that has a
decent build system, so building it isn't hard either way.
On Friday, January 10, 2014 1:04:09 AM UTC-10, mmarco wrote:
>
> So we would use python to run the buildiing scripts for the sage
> components... including python its
On Jan 8, 2014 6:27 PM, "kcrisman" wrote:
>
>
>
> On Wednesday, January 8, 2014 7:24:19 PM UTC-5, William wrote:
>>
>> Hi,
>>
>> There is going to be Sage / SageMathCloud booth at the Joint
>> Mathematics Meetings in Baltimore next week. Like last year, I'm
>> planning to be there *most* of the t
I get the same error as Simon!
Anne
On Wednesday, January 8, 2014 10:40:24 AM UTC-8, Simon King wrote:
>
>
>
> Am Dienstag, 7. Januar 2014 17:23:53 UTC+1 schrieb Nicolas M. Thiéry:
>>
>>
>> Did anyone stumble on errors like this when compiling the
>> documentation?
>>
>>
> I just met a very sim
FTR, I'm trying right now.
Best,
Travis
On Friday, January 10, 2014 8:51:20 AM UTC-8, anne1.s...@gmail.com wrote:
>
>
>
> On Friday, January 10, 2014 8:30:12 AM UTC-8, Jeroen Demeyer wrote:
>>
>> On 2014-01-10 17:23, Anne Schilling wrote:
>> > Any objections?
>> I thought the policy was to *ne
On 2014-01-06 22:46, Zimmermann Paul wrote:
Nils,
Date: Mon, 6 Jan 2014 13:18:07 -0800 (PST)
From: Nils Bruin
On Monday, January 6, 2014 12:46:19 PM UTC-8, Zimmermann Paul wrote:
What about getting rid of real literals?
I think they exist mainly to let
RealField(200)(1e-20)
wor
Hi Robert,
On Tue, Jan 07, 2014 at 02:30:09PM -0800, Robert Bradshaw wrote:
> Does anyone know how to reproduce this? It does look like a dependency
> checking error, which I'd like to fix.
I reproduced the error on sagemath.org. Currently if I run `make doc`
in /home/nthiery/sage-6.0 I g
On Friday, January 10, 2014 8:30:12 AM UTC-8, Jeroen Demeyer wrote:
>
> On 2014-01-10 17:23, Anne Schilling wrote:
> > Any objections?
> I thought the policy was to *never* remove old pickles?
>
It was suggested by Volker, see
http://trac.sagemath.org/ticket/15575#comment:39
Otherwise, can
On 2014-01-10 17:23, Anne Schilling wrote:
Any objections?
I thought the policy was to *never* remove old pickles?
--
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
t
Hi!
We would like to remove the pickles
_class__sage_combinat_sf_kschur_kSchurFunctions_t__.sobj
which come from an old implementation of k-Schur functions. This class
was deprecated for a year and has now been removed.
Any objections?
Anne
--
You received this message because you are subscr
On Friday, January 10, 2014 2:02:52 AM UTC-8, Stefan wrote:
> On a git ticket, click on the name of the branch (which should be green if
>> it applies cleanly) and you'll get a diff of the changes that would occur
>> if the ticket were merged into the current development branch. This view
>>
It was already deprecated (5 years ago). #15661 removes it :
http://trac.sagemath.org/ticket/15661
Nathann
--
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-de
Hello Guys ! Just sharing a funny adventure :
I have a function with an argument F that can be a finite field, or an
integer (its cardinality).
try:
my_integer = F.order()
except AttributeError:
my_integer = F
Does it work ?
No, because :
sage: 9.order()
+Infinity
Ahahaha.
Nathann
-
So we would use python to run the buildiing scripts for the sage
components... including python itself?
Maybe it is better in the long term, but it sounds weird.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and
> On a git ticket, click on the name of the branch (which should be green if
> it applies cleanly) and you'll get a diff of the changes that would occur
> if the ticket were merged into the current development branch. This view
> won't be affected by the kind of rebases that you mention.
>
O
Ah thanks, that answers my immediate questions, so you can ignore the other
posting about GSoC13 work (it appears that part is working fine).
On Friday, January 10, 2014 8:16:00 AM UTC+1, Volker Braun wrote:
>
> Rasmi Elasmar changed the communication to support web sockets during GSoC
> 2013. I
16 matches
Mail list logo
