On Wednesday, March 9, 2011, kcrisman wrote:
> Before the review, a tidbit from "97 Things Every Programmer Should
> Know" - #93, I think (page 186-7):
>
> Write Code As If you Had to Support It for the Rest of Your Life
>
> Now to our main story.
>
> I love the new books section of any academic l
Hello everybody !!
I am trying to fill some doctests in the numerical/ folder, and it
looks like the -coverage flag does not like to see methods raising
exceptions...
sage -coverage sage/numerical/backends/cplex_backend.pyx
Missing documentation:
* int add_variable(self, lower_bound=0.0
2011/3/9 Francois Bissey :
>> This may be of interest
>>
>>
>> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doo
>> med_to_FAIL
>>
>> and should explain why sage is not included and/or built from
>> sources in any major distro. Well, I make rpms for Mandriva,
>> and ther
On Mar 9, 1:30 pm, Harald Schilly wrote:
> Is this already a ticket on trac? if not, please go ahead and open a new
> ticket athttp://trac.sagemath.organd explain this there.
I've created ticket #10895 for this.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscri
Before the review, a tidbit from "97 Things Every Programmer Should
Know" - #93, I think (page 186-7):
Write Code As If you Had to Support It for the Rest of Your Life
Now to our main story.
I love the new books section of any academic library. Today, I
checked out the interesting-sounding "Dat
> This may be of interest
>
> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doo
> med_to_FAIL
>
> and should explain why sage is not included and/or built from
> sources in any major distro. Well, I make rpms for Mandriva,
> and there is the gentoo port...
>
My turn?
> Which is why he didn't count them. Of course most of those points
> would be big negative marks against any distribution system, and they
> should all be taken with a boulder-sized grain of salt. I think we
> have more than enough "points of success" to counter out these "points
> of fail." :-)
Hi all,
We are pleased to announce the release of flint 2.1. It can be
obtained at the flint website:
http://www.flintlib.org/
For those who want to go straight to the benchmarking pr0n (missing
times are estimated to vary up to at least 6 MONTHS -- we think this
is the first time flint may be 7
On Wed, Mar 9, 2011 at 4:35 PM, Tom Boothby wrote:
> 2011/3/9 Paulo César Pereira de Andrade
> :
>
>> But I did not account:
>> Releases
>> - Your releases are only in an encapsulation format that you invented.
>> [ +100 points of FAIL ]
>> (( spkgs ))
>
> To be fair, .spkg == tar.bz2, so these
2011/3/9 Paulo César Pereira de Andrade
:
> But I did not account:
> Releases
> - Your releases are only in an encapsulation format that you invented.
> [ +100 points of FAIL ]
> (( spkgs ))
To be fair, .spkg == tar.bz2, so these hundred points are unfair.
2011/3/9 William Stein :
> I'm glad
2011/3/9 Paulo César Pereira de Andrade
:
> This may be of interest
>
> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL
Did he used rand() to come up with those numbers? There does not
appear to be any justification for the numbers, or the conclusions
that h
2011/3/9 Paulo César Pereira de Andrade
:
> 2011/3/9 Harald Schilly :
>
> I understand that this kind of post, besides attempting to state it is a
> friendly one, could cause more harm than good. The TV show probably
> would have a small specialized audience :-) But the rants/discussions,
> and eg
On Sat, Mar 05, 2011 at 07:48:06PM -0800, kcrisman wrote:
>
>
> On Mar 5, 10:26 pm, Jason Grout wrote:
> > On 3/5/11 7:48 PM, kcrisman wrote:
> >
> >
> >
> >
> >
> >
> >
> > > On Mar 5, 10:51 am, Jason Grout wrote:
> > >> On 3/5/11 9:21 AM, Bill Page wrote:
> >
> > >>> Oops, sorry I spoke too q
2011/3/9 Harald Schilly :
I understand that this kind of post, besides attempting to state it is a
friendly one, could cause more harm than good. The TV show probably
would have a small specialized audience :-) But the rants/discussions,
and ego wars (not so much as in some other projects) that
2011/3/9 Paulo César Pereira de Andrade
:
> This may be of interest
>
> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL
>
> and should explain why sage is not included and/or built from
> sources in any major distro. Well, I make rpms for Mandriva,
> and ther
On Wed, Mar 9, 2011 at 2:07 PM, Harald Schilly wrote:
> exactly how did you come up with 280 points?
> quoting to box on top:
> """There are obvious exceptions, such as the Linux kernel. Generally these
> exceptions work because they started out small and the community and code
> grew together. ""
exactly how did you come up with 280 points?
quoting to box on top:
"""There are obvious exceptions, such as the Linux kernel. Generally these
exceptions work because they started out small and the community and code
grew together. """
Therefore I'm glad Sage started <17mb and grew slowly:
http
I wonder... can we make money off of said reality TV show?
2011/3/9 Paulo César Pereira de Andrade
:
> This may be of interest
>
> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL
>
> and should explain why sage is not included and/or built from
> sources in
This may be of interest
https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL
and should explain why sage is not included and/or built from
sources in any major distro. Well, I make rpms for Mandriva,
and there is the gentoo port...
My last work on a sagemath
The only safe way is an autoconf-style test or something that uses that (for
example, the output of platform.architecture() in python).
One particular caveat is that on OSX the kernel bitness is usually different
from the userspace bitwidth, and you are bound to pick up the wrong one if
you ar
On 9 March 2011 16:53, Jan Raasch wrote:
> Thank you, Bill, you are right. After having a closer look at the
> mpir-1.2.2.p2.spkg file I found that there is a function inside the
> spkg-install file called
>
> remove_pic_osx_32_bit()
>
> which does exactly what you suggested (It deletes the asm fi
Hi, sounds interesting!
Is this already a ticket on trac? if not, please go ahead and open a new
ticket at http://trac.sagemath.org and explain this there.
Mercurial is only used *inside* an spkg to track its internal changes once a
version has been deployed - using git for your code is no pro
I've worked up a python module and an associated spkg that basically
wraps numpy in a way that makes it useful for doing finite-dimensional
quantum mechanics over several particles. In particular, this should
be useful for quantum information. I have only six months of
experience with python, so
Thank you, Bill, you are right. After having a closer look at the
mpir-1.2.2.p2.spkg file I found that there is a function inside the
spkg-install file called
remove_pic_osx_32_bit()
which does exactly what you suggested (It deletes the asm files that
have the problem). Here is the part of the co
On Wednesday, March 9, 2011 1:22:11 PM UTC+1, Simon King wrote:
>
> Both answers are correct.
>
>
What about
sage: answ = K.selmer_group(...)
sage: answ == [2, a + 1, a] or answ = [2, a + 1, -a]
True
?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe fr
Interesting. Thank you for pointing this out (and for the ticket
reference). Apparently there is somebody working on that already.
Regards,
Gustavo
On Mar 9, 1:22 pm, Simon King wrote:
> Both answers are correct.
>
> However, that test is pretty annoying, since apparently the exact
> result is
Hi Gustavo,
On 9 Mrz., 12:22, Gustavo de Oliveira wrote:
> Test output:
>
> sage -t "devel/sage/sage/rings/number_field/number_field.py"
> **
> File "/home/goliveir/local/sage-4.6.2/devel/sage/sage/rings/
> number_field/number_f
I few days ago I downloaded and installed Sage 4.6.2 from source. It
compiled without errors in my computer. Then I run 'make test' and I
got an error in number_field.py. I reproduced the error with the
command
$ ./sage -t devel/sage/sage/rings/number_field/number_field.py
The test output is atta
28 matches
Mail list logo
