Hello, David.
> Is license info available?
I've contacted Stephen Moshier several years ago and he made it clear
that anyone can use Cephes under any license (as long as copyright is
preserved).
I think that someone can contact him and ask for the explicit
permission to license Cephes
On 26 May 2010 02:16, Mike Hansen wrote:
> Hello,
>
> I propose to make Cephes ( http://moshier.net/ and
> http://www.netlib.org/cephes/ ) a standard SPKG in Sage. In order to
> complete the Cygwin port on Windows, we need support for c99 complex
> numbers which the SPKG provides (amongst other t
In fact, I'm not sure the term "Bezout coefficients" is standard, but
you can find it on Wikipedia.
http://en.wikipedia.org/wiki/B%C3%A9zout%27s_identity
They also call these "Bezout numbers", since they're linked to the
Bezout identity.
Alex
On 25 mai, 16:44, Robert Bradshaw
wrote:
> On May 25,
Please see http://trac.sagemath.org/sage_trac/ticket/9003 for
details. The reason I'm bringing this up on sage-devel is that
apparently (I can't really believe this is the actual reason, which is
why I say apparently) the following changeset causes a totally
unrelated failure - one which does NOT
On Tue, May 25, 2010 at 7:05 PM, David Joyner wrote:
> On Tue, May 25, 2010 at 10:00 PM, Mike Hansen wrote:
>> On Tue, May 25, 2010 at 6:56 PM, Jason Grout
>> wrote:
>>> On 5/25/10 8:49 PM, David Joyner wrote:
Is license info available?
>>
>> It's included in Debian as GPL -- we c
On Tue, May 25, 2010 at 10:00 PM, Mike Hansen wrote:
> On Tue, May 25, 2010 at 6:56 PM, Jason Grout
> wrote:
>> On 5/25/10 8:49 PM, David Joyner wrote:
>>>
>>> Is license info available?
>>>
>
> It's included in Debian as GPL -- we can just obtain a copy from them. See
>
> http://www.mail-archiv
On Tue, May 25, 2010 at 6:56 PM, Jason Grout
wrote:
> On 5/25/10 8:49 PM, David Joyner wrote:
>>
>> Is license info available?
>>
It's included in Debian as GPL -- we can just obtain a copy from them. See
http://www.mail-archive.com/debian-bugs-clo...@lists.debian.org/msg165325.html
--Mike
--
On Tue, May 25, 2010 at 9:56 PM, Jason Grout
wrote:
> On 5/25/10 8:49 PM, David Joyner wrote:
>>
>> Is license info available?
>>
>
> According to http://www.netlib.org/cephes/readme
>
>
> Some software in this archive may be from the book _Methods and
> Programs for Mathematical Functions_ (Pre
On 5/25/10 8:49 PM, David Joyner wrote:
Is license info available?
According to http://www.netlib.org/cephes/readme
Some software in this archive may be from the book _Methods and
Programs for Mathematical Functions_ (Prentice-Hall or Simon & Schuster
International, 1989) or from the Ceph
Is license info available?
On Tue, May 25, 2010 at 9:16 PM, Mike Hansen wrote:
> Hello,
>
> I propose to make Cephes ( http://moshier.net/ and
> http://www.netlib.org/cephes/ ) a standard SPKG in Sage. In order to
> complete the Cygwin port on Windows, we need support for c99 complex
> numbers
On Tue, May 25, 2010 at 6:16 PM, Mike Hansen wrote:
> Hello,
>
> I propose to make Cephes ( http://moshier.net/ and
> http://www.netlib.org/cephes/ ) a standard SPKG in Sage. In order to
> complete the Cygwin port on Windows, we need support for c99 complex
> numbers which the SPKG provides (amon
Hello,
I propose to make Cephes ( http://moshier.net/ and
http://www.netlib.org/cephes/ ) a standard SPKG in Sage. In order to
complete the Cygwin port on Windows, we need support for c99 complex
numbers which the SPKG provides (amongst other things). The SPKG can
be found at #8780. The spkg wi
I couldnt see a solution to this in this thread so heres a related question
The following produces the exact output Id like to produce (to assign to the
_repr_ property of a class)
%latex
N(\mu,\sigma^2)
How can I set things up to do this in a (_repr_) function (as a sage
statement/function cal
Hi,
If you've very interested in attending Sage Days 23
http://wiki.sagemath.org/days23
Please send me an offlist email. There may be some funding left for
additional people (mainly lodging and possibly travel within Europe).
It would be good to have a few more people around at that worksh
On May 25, 2010, at 1:42 PM, ablondin wrote:
Thanks !
I would never have guessed the name !
Alex
And I had never heard of the term "Bezout coefficients" :). The is an
abbreviation for "extended gcd."
On 25 mai, 16:28, Tim Daly wrote:
Is anyone else getting duplicate copies of Sage messa
Way to go... this would be excellent - instant scalable sage
computing:
check out the kind of thing BIx folks are doing for the community:
http://bcbio.wordpress.com/2010/05/08/automated-build-environment-for-bioinformatics-cloud-images/
You have to get sage into this party - actually I think a
Thanks !
I would never have guessed the name !
Alex
On 25 mai, 16:28, Tim Daly wrote:
> Is anyone else getting duplicate copies of Sage messages? -- Tim
>
> Mike Hansen wrote:
> > Hello,
>
> >> I've been looking for a function that allows one to compute Bezout
> >> coefficients of two numbers (sa
Is anyone else getting duplicate copies of Sage messages? -- Tim
Mike Hansen wrote:
Hello,
I've been looking for a function that allows one to compute Bezout
coefficients of two numbers (say natural numbers). There is the GCD
function, but I haven't found anything about Bezout coefficients.
On May 25, 2010, at 1:17 PM, Jason Grout wrote:
On 5/25/10 3:07 PM, kcrisman wrote:
There remains one additional problem. If we have been putting long
information into SPKG.txt for a while with almost no information in
the commit messages, getting rid of the SPKG.txt ones will leave a
fai
On May 25, 2010, at 1:11 PM, Jason Grout wrote:
On 5/25/10 2:56 PM, William A. Stein wrote:
On May 25, 2010, at 12:30 PM, Jason Grouts...@creativetrax.com> wrote:
On 5/25/10 2:01 PM, Robert Bradshaw wrote:
On May 25, 2010, at 11:50 AM, William Stein wrote:
Having info about patches is
On 5/25/10 3:07 PM, kcrisman wrote:
There remains one additional problem. If we have been putting long
information into SPKG.txt for a while with almost no information in
the commit messages, getting rid of the SPKG.txt ones will leave a
fairly large piece of their history mysterious at bes
On Tue, May 25, 2010 at 12:56 PM, William A. Stein wrote:
> Interesting. If I remember correctly, you and I had a long discussion about
> those patch files, in which I was totally against them, and you argued for
> them. I think they are there now mostly because of you. I'm still against
>
On 5/25/10 2:56 PM, William A. Stein wrote:
On May 25, 2010, at 12:30 PM, Jason Grout wrote:
On 5/25/10 2:01 PM, Robert Bradshaw wrote:
On May 25, 2010, at 11:50 AM, William Stein wrote:
Having info about patches is a good idea. I'm definitely not
convinced SPKG.txt is the right plac
Hello,
> I've been looking for a function that allows one to compute Bezout
> coefficients of two numbers (say natural numbers). There is the GCD
> function, but I haven't found anything about Bezout coefficients. This
> is not complicated to write one, but it would be better if it was
> included
> > And I reiterate that I recall somewhere a suggestion on sage-devel
> > that commit messages should be one line long. Does no one else
> > remember that? Or did it mean it should not have any carriage
> > returns, but be as long as it wants (in which case this was not clear
> > at all)?
>
> O
On May 24, 9:11 pm, ablondin
wrote:
> You're right ! It doesn't work with the view() function. On the other
> hand, when I select latex instead of sage and I enter the command
>
> \sage{A()}
>
> it displays 123 on the first line and 23 on the second line, with the
> 2's aligned properly, i.e. it h
Hello, everyone !
I've been looking for a function that allows one to compute Bezout
coefficients of two numbers (say natural numbers). There is the GCD
function, but I haven't found anything about Bezout coefficients. This
is not complicated to write one, but it would be better if it was
included
On May 25, 2010, at 12:35 PM, kcrisman wrote:
On May 25, 3:05 pm, William Stein wrote:
On Tue, May 25, 2010 at 12:02 PM, kcrisman
wrote:
changelog, where it will scroll off the bottom and be forgotten.
I'd
This is my main point, as well as for those who in the future will
just be lear
On 5/25/10 2:52 PM, William A. Stein wrote:
+1 to Robert's comments. Already, I don't ever make or use foo.patch files
anymore because they are completely redundant and one more easily-forgotten
step to make (they should be totally automated if they are required).
Interesting
I'm not s
On May 25, 2010, at 12:30 PM, Jason Grout wrote:
> On 5/25/10 2:01 PM, Robert Bradshaw wrote:
>> On May 25, 2010, at 11:50 AM, William Stein wrote:
>>
>
>
>>> Having info about patches is a good idea. I'm definitely not
>>> convinced SPKG.txt is the right place for it. I would install prop
On May 25, 2010, at 12:30 PM, Jason Grout wrote:
> On 5/25/10 2:01 PM, Robert Bradshaw wrote:
>> On May 25, 2010, at 11:50 AM, William Stein wrote:
>>
>
>
>>> Having info about patches is a good idea. I'm definitely not
>>> convinced SPKG.txt is the right place for it. I would install prop
On May 25, 3:05 pm, William Stein wrote:
> On Tue, May 25, 2010 at 12:02 PM, kcrisman wrote:
> >> changelog, where it will scroll off the bottom and be forgotten. I'd
>
> > This is my main point, as well as for those who in the future will
> > just be learning hg and find going the right direct
Hello, Bill.
> In fact, unless I am mistaken refresh your browser!
> Now let's all forget this ever happened and let's get on with our jobs.
+1!
--
With best regards,
Sergey mailto:sergey.bochka...@alglib.net
--
To post to this group, send an email to sage-devel@
On 5/25/10 2:01 PM, Robert Bradshaw wrote:
On May 25, 2010, at 11:50 AM, William Stein wrote:
Having info about patches is a good idea. I'm definitely not
convinced SPKG.txt is the right place for it. I would install propose
something *like* for every patch foo, having a file foo.wtf (or
som
On Tue, May 25, 2010 at 12:02 PM, kcrisman wrote:
>> changelog, where it will scroll off the bottom and be forgotten. I'd
>
> This is my main point, as well as for those who in the future will
> just be learning hg and find going the right directory etc.
> difficult.
sage -hg log |more
??
>
> A
On May 25, 2010, at 11:50 AM, William Stein wrote:
On Tue, May 25, 2010 at 11:36 AM, Robert Bradshaw
wrote:
On May 25, 2010, at 11:26 AM, Jason Grout wrote:
On 5/25/10 12:41 PM, Robert Bradshaw wrote:
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a
changelog entr
> changelog, where it will scroll off the bottom and be forgotten. I'd
This is my main point, as well as for those who in the future will
just be learning hg and find going the right directory etc.
difficult.
As for HISTORY.txt, I don't understand why that isn't updated, since
http://www.sagema
On Tue, May 25, 2010 at 11:36 AM, Robert Bradshaw
wrote:
> On May 25, 2010, at 11:26 AM, Jason Grout wrote:
>
>> On 5/25/10 12:41 PM, Robert Bradshaw wrote:
>>>
>>> Hi all,
>>>
>>> I just had a new spkg (rightly) rejected because it didn't have a
>>> changelog entry in SPKG.txt , as specified by [
On 5/25/10 1:23 PM, kcrisman wrote:
On May 25, 1:50 pm, William Stein wrote:
On Tue, May 25, 2010 at 10:41 AM, Robert Bradshaw
wrote:
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a changelog
entry in SPKG.txt , as specified by [1], Does anyone know why are we
On May 25, 2010, at 11:26 AM, Jason Grout wrote:
On 5/25/10 12:41 PM, Robert Bradshaw wrote:
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a
changelog entry in SPKG.txt , as specified by [1], Does anyone know
why
are we manually keeping a text changelog when the fi
On Tue, May 25, 2010 at 11:23 AM, kcrisman wrote:
>
>
> On May 25, 1:50 pm, William Stein wrote:
>> On Tue, May 25, 2010 at 10:41 AM, Robert Bradshaw
>>
>> wrote:
>> > Hi all,
>>
>> > I just had a new spkg (rightly) rejected because it didn't have a changelog
>> > entry in SPKG.txt , as specifie
On May 25, 2010, at 11:23 AM, kcrisman wrote:
On May 25, 1:50 pm, William Stein wrote:
On Tue, May 25, 2010 at 10:41 AM, Robert Bradshaw
wrote:
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a
changelog
entry in SPKG.txt , as specified by [1], Does anyone know
On 5/25/10 12:41 PM, Robert Bradshaw wrote:
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a
changelog entry in SPKG.txt , as specified by [1], Does anyone know why
are we manually keeping a text changelog when the files under our
control are already under revision contr
On May 25, 1:50 pm, William Stein wrote:
> On Tue, May 25, 2010 at 10:41 AM, Robert Bradshaw
>
> wrote:
> > Hi all,
>
> > I just had a new spkg (rightly) rejected because it didn't have a changelog
> > entry in SPKG.txt , as specified by [1], Does anyone know why are we
> > manually keeping a t
In fact, unless I am mistaken refresh your browser!
Now let's all forget this ever happened and let's get on with our jobs.
Bill.
On 25 May 2010 18:47, Bill Hart wrote:
> My point is, imagine how damaging it will be to the author of those
> comments if they just leave them there. Trust me,
On Tue, May 25, 2010 at 10:41 AM, Robert Bradshaw
wrote:
> Hi all,
>
> I just had a new spkg (rightly) rejected because it didn't have a changelog
> entry in SPKG.txt , as specified by [1], Does anyone know why are we
> manually keeping a text changelog when the files under our control are
> alrea
My point is, imagine how damaging it will be to the author of those
comments if they just leave them there. Trust me, they'll go of their
own accord. We don't need to touch this one.
If someone else feels strongly that action needs to be taken, well I
won't be getting in their way. As for me, on w
Hi all,
I just had a new spkg (rightly) rejected because it didn't have a
changelog entry in SPKG.txt , as specified by [1], Does anyone know
why are we manually keeping a text changelog when the files under our
control are already under revision control?
- Robert
[1] http://www.sagemath
Hello, Bill.
> So it is established that we are being accused of academic fraud for
> removing the author information WHEN IT WAS DONE BY SOMEONE ON THE GMP
> TEAM in the actual version of GMP we forked from!!
Confirmed.
> I think what is currently on the GMP website is FAR more damaging to
> t
On Tue, May 25, 2010 at 9:17 AM, Tom Boothby wrote:
> +1 to using Graph6 strings, and I'll review this tomorrow.
OK, the doctest is in the patch, and all ready for review.
--
Robert L. Miller
http://www.rlmiller.org/
--
To post to this group, send an email to sage-devel@googlegroups.com
To u
+1 to using Graph6 strings, and I'll review this tomorrow.
On Tue, May 25, 2010 at 9:12 AM, Robert Miller wrote:
> Fixed!
>
> http://trac.sagemath.org/sage_trac/ticket/9045
>
> Note that the patch does not yet have any doctests. I'm waiting on a
> better description of the graphs which caused the
Fixed!
http://trac.sagemath.org/sage_trac/ticket/9045
Note that the patch does not yet have any doctests. I'm waiting on a
better description of the graphs which caused the bug in the first
place. (Although we could use the graph6 strings for now, since having
this merged is probably pretty impor
Added information to the ticket http://trac.sagemath.org/sage_trac/ticket/9003
Kwankyu Lee
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http:/
Oh, this is absolutely delicious!
Here is the author information from the gmp-4.2.1.tar.gz in doc/gmp.texi:
@c @author by Torbj@"orn Granlund, Swox AB
@c @email{tege@@swox.com}
Note the @c comments here, which as far as I see, do indeed comment
out the author information!! I invite people to che
Hello, Bill.
> Now, we are looking into why this isn't appearing on the title page of
> the pdf documentation. That appears to be a technical issue! We will
> also add "The GMP Development Team" as per the latest GMP
> documentation.
I think that when you fix _everything_ someone still will be
On May 25, 8:39 am, leif wrote:
> On 25 Mai, 14:01, Kwankyu Lee wrote:
>
> > This doctest failure did not occur without applying my own patch, so I
> > thought my patch was the cause. A weird bug indeed...
>
> Interesting. Is this behavior reproducable (i.e. present in all test
> runs)?
Yes, p
On 25 Mai, 14:01, Kwankyu Lee wrote:
> This doctest failure did not occur without applying my own patch, so I
> thought my patch was the cause. A weird bug indeed...
Interesting. Is this behavior reproducable (i.e. present in all test
runs)?
Is your patch on trac? This could help narrowing the o
Hi Leif,
This doctest failure did not occur without applying my own patch, so I
thought my patch was the cause. A weird bug indeed...
Thank you for the pointers.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sa
Someone has just pointed out that the mpir.texi document, from which
our pdf documentation is generated contains:
@c @author Original version by Torbj@"orn Granlund, Swox AB - modified
by William Hart
@c @email{goodwillh...@gmail.com}
So, not only did we not remove the original author information
On 25 Mai, 11:41, leif wrote:
> This is a known issue, and most probably ;-) not related to your
> patch:
>
> See e.g.http://groups.google.com/group/sage-release/msg/dac6cb862ecf6a8e
Direct link to the ticket:
http://trac.sagemath.org/sage_trac/ticket/9003
-Leif
--
To post to this group, send
On 25 Mai, 11:30, Kwankyu Lee wrote:
> Hi,
>
> I am debugging a patch of my own. Perhaps due to the patch, I get the
> following strange doctest failure.
>
> sage -t "4.4.2/devel/sage-main/sage/modules/free_module.py"
> **
> File
On 25 Mai, 11:18, leif wrote:
> What I wanted to say is that installing another version of gcc in /usr/
> local on systems (like Linux distros) where there already is a
> "native" one (gcc) in /usr is non-trivial, i.e. this doesn't work "out
> of the box".
>
> With the "native" gcc, "-lstdc++" is
> On May 25, 11:14 am, François Bissey wrote:
> Thats no more correct on gentoo - I have written a set of sed commands
> which fixes this behaviour:
>
> http://github.com/cschwan/sage-on-gentoo/blob/master/sci-mathematics/sympow
> /sympow-1.018.ebuild
>
> (see lines 27 to 55).
>
> I think this
Hi,
I am debugging a patch of my own. Perhaps due to the patch, I get the
following strange doctest failure.
sage -t "4.4.2/devel/sage-main/sage/modules/free_module.py"
**
File "/Users/Kwankyu/Sage/sage-4.4.2/devel/sage-main/sag
On May 25, 11:14 am, François Bissey wrote:
> Hi,
>
> sympow is a weird program. Not really completely standard. The problem
> is the datafiles folder for the data generated by sympow must be in the
> same folder as the one containing the executables and the sympow scripts.
> Which is a lot of fun
On 25 Mai, 02:13, "Dr. David Kirkby" wrote:
> On 05/24/10 05:26 PM, leif wrote:
>
> > Looks like the (fairly old) gcc/g++ in /usr/local is misconfigured; it
> > definitely tries to link a 64-bit (x86_64) C++ program against the 32-
> > bit libstdc++.so (in /usr/local/lib) instead of the 64-bit ver
> When on builds 'sympow', a directory $SAGE_LOCAL/lib/sympow is made, and
> the file 'sympow' executable copied there:
>
> drkir...@hawk:~/sage-4.4.2$ ./local/lib/sympow/sympow
> sympow 1.018 RELEASE (c) Mark Watkins --- see README and COPYING for
> details
>
>
> It seems a strange decision t
I agree!
John
On 25 May 2010 08:44, Dr. David Kirkby wrote:
> When on builds 'sympow', a directory $SAGE_LOCAL/lib/sympow is made, and
> the file 'sympow' executable copied there:
>
> drkir...@hawk:~/sage-4.4.2$ ./local/lib/sympow/sympow
> sympow 1.018 RELEASE (c) Mark Watkins --- see README a
On 25 Mai, 09:07, Robert Miller wrote:
combinations higher up.
> [...]
> Now that I understand the bug, my experience is it's best to sleep on
> it, and tackle fixing it tomorrow. This way I've given myself a nice
> outline towards doing that...
This is good practice not just for fixing bugs.
Can
When on builds 'sympow', a directory $SAGE_LOCAL/lib/sympow is made, and the
file 'sympow' executable copied there:
drkir...@hawk:~/sage-4.4.2$ ./local/lib/sympow/sympow
sympow 1.018 RELEASE (c) Mark Watkins --- see README and COPYING for details
It seems a strange decision to copy an execut
Ok, in case I get hit by lightning in the next twelve hours, I've at
least figured out what the bug is, but fixing it will take some
effort. Essentially, the bug is in double_coset.pyx, when we do the
first set of refinements to get the left partition stack and the first
partition stack set up. The
71 matches
Mail list logo
