On Feb 8, 2012, at 1:18 AM, Jason Grout wrote:
> On 2/7/12 4:28 PM, Ivan Andrus wrote:
>> I'm fairly certain #11881 (which still needs review) will solve the problem.
>> At least the most common problem.
>
> Do you, by chance, mean http://trac.sagemath.org/sage_trac/ticket/12161
>
> #11881 is
On Wed, Feb 8, 2012 at 14:25, Keshav Kini wrote:
> Thunderbox
Er. Thunderbird.
-Keshav
Join us in #sagemath on irc.freenode.net !
--
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.c
On Mon, Feb 6, 2012 at 11:33, William Stein wrote:
>> More concerning is the lack of support for Google
>> Groups from the Data Liberation Front at Google. If our group gets
>> shut down for whatever reason, do we have a backup of all messages?
>> How can we get a backup?
>
> I'm subscribed to al
Done!
-Keshav
Join us in #sagemath on irc.freenode.net !
--
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://groups.google.com/group/sag
> +100. Our main problem with Mercurial is that we are not *using* it. We
> are just using Mercurial as a way for Jeroen to generate changelogs, and no
> other collaborative purpose whatsoever (despite what individual developers
> such as William might be doing with qfinishing patches, committing,
Sorry, I managed to activate some button on Google Groups accidentally and
prematurely post the above message...
+100. Our main problem with Mercurial is that we are not *using* it. We are
just using Mercurial as a way for Jeroen to generate changelogs, and no
other collaborative purpose whatso
+100.
--
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://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
+1
I had to go look up what GSOC was first ...
Jt
On Feb 7, 2012 11:27 PM, "Jason Aubrey" wrote:
> On Tue, Feb 7, 2012 at 11:17 PM, kcrisman wrote:
>
>> >
>> > * overhaul 2d graphics to be consistent, take advantage of matplotlib
>> > much more, etc. Introduce svg or html5 frontends for matpl
On Tue, Feb 7, 2012 at 11:17 PM, kcrisman wrote:
> >
> > * overhaul 2d graphics to be consistent, take advantage of matplotlib
> > much more, etc. Introduce svg or html5 frontends for matplotlib that
> > make interactive browser graphics easier (like interacts)
>
> These would be really cool.
>
>
> * overhaul 2d graphics to be consistent, take advantage of matplotlib
> much more, etc. Introduce svg or html5 frontends for matplotlib that
> make interactive browser graphics easier (like interacts)
These would be really cool.
> * webwork/sage integration
There are real people already wor
On 2/7/12 10:15 PM, William Stein wrote:
On Tue, Feb 7, 2012 at 8:11 PM, Volker Braun wrote:
Maybe we can tie the Android app into the notebook work? I could help mentor
a student working on Android stuff, maybe that would help our GSOC
application.
That's an *extremely* good idea!
Maybe we
>
> > I'd be willing to mentor, for example, a notebook project, since that's what
> > I'll be working on most of the summer. I'll already have several students
> > hopefully working with me on the notebook, or graphics (webgl, here we come
> > :), etc.
>
> Excellent. I am also willing to mentor
On Tue, Feb 7, 2012 at 8:11 PM, Volker Braun wrote:
> Maybe we can tie the Android app into the notebook work? I could help mentor
> a student working on Android stuff, maybe that would help our GSOC
> application.
That's an *extremely* good idea!
Maybe we should have "The Sage Notebook" as the
On Tue, Feb 7, 2012 at 8:11 PM, kcrisman wrote:
>>
>> If I find a little time I may yet try this tonight, since ...
>>
>
> I can't reproduce this even if I do
>
> mv .sage/ .oldsage
>
> with the "sketchy" binary in question. It must be highly dependent on
> a lot of stuff :( sorry.
Yes, I've nev
Maybe we can tie the Android app into the notebook work? I could help
mentor a student working on Android stuff, maybe that would help our GSOC
application.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubs
>
> If I find a little time I may yet try this tonight, since ...
>
I can't reproduce this even if I do
mv .sage/ .oldsage
with the "sketchy" binary in question. It must be highly dependent on
a lot of stuff :( sorry.
--
To post to this group, send an email to sage-devel@googlegroups.com
To u
On Tue, Feb 7, 2012 at 7:55 PM, Jason Grout wrote:
> On 2/7/12 9:48 PM, William Stein wrote:
>>
>> Hi,
>>
>> Does anybody want to help put together a GSoC application for Sage for
>> 2012?
>>
>> http://code.google.com/soc/
>>
>> The application deadline is March 9.
>>
>> So far, I think we've a
On 2/7/12 9:48 PM, William Stein wrote:
Hi,
Does anybody want to help put together a GSoC application for Sage for 2012?
http://code.google.com/soc/
The application deadline is March 9.
So far, I think we've applied 5 times to have Sage as a mentoring
organizing, and been denied every tim
Hi,
Does anybody want to help put together a GSoC application for Sage for 2012?
http://code.google.com/soc/
The application deadline is March 9.
So far, I think we've applied 5 times to have Sage as a mentoring
organizing, and been denied every time. I think there is no feedback
about why
On Feb 7, 2:34 pm, William Stein wrote:
> Hi,
>
> I just got yet another (almost daily now) bug report about our OS X
> binaries being complete crap. This time from a Fields Medalist! So
> why don't we deal with this?
William, on a related note, have all the people who used your
4.8.alpha3 or
On Tuesday, February 7, 2012 3:06:14 PM UTC-8, Jeroen Demeyer wrote:
>
> I came across the following in the Sage Developer guide:
>
>- If your package depends on another package, say boehmgc, then you
> should check that this other package has been installed. Your
> ``spkg-install``
On 2/7/12 4:28 PM, Ivan Andrus wrote:
I'm fairly certain #11881 (which still needs review) will solve the problem.
At least the most common problem.
Do you, by chance, mean http://trac.sagemath.org/sage_trac/ticket/12161
#11881 is a huge ticket with lots of patches.
Thanks,
Jason
Has
On Wednesday, February 8, 2012 7:06:14 AM UTC+8, Jeroen Demeyer wrote:
>
> I came across the following in the Sage Developer guide:
>
>- If your package depends on another package, say boehmgc, then you
> should check that this other package has been installed. Your
> ``spkg-install
See http://trac.sagemath.org/sage_trac/ticket/12449
I made a patch to change the way that sage evaluates symbolic functions for
basic python types, and at the same time changed RDF to just use
math.gamma() instead of gsl's gamma function.
(Note: math.gamma() should be available in sage-5.0 (pytho
On Wednesday, February 8, 2012 3:34:38 AM UTC+8, William wrote:
>
> Hi,
>
> I just got yet another (almost daily now) bug report about our OS X
> binaries being complete crap. This time from a Fields Medalist! So
> why don't we deal with this?
>
> The traceback he sent me is exactly the same as t
On 7 February 2012 16:38, William Stein wrote:
> On Mon, Feb 6, 2012 at 3:42 PM, Dr. David Kirkby
> wrote:
> > On 02/ 6/12 09:09 AM, Jeroen Demeyer wrote:
> >>
> >> On 2012-02-06 09:33, Dr. David Kirkby wrote:
> >>>
> >>> I think trying to replicate autotools would be just silly.
> >>
> >> That'
As the PPL packager I'm fine with this ;-)
--
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://groups.google.com/group/sage-devel
URL: http:/
I came across the following in the Sage Developer guide:
- If your package depends on another package, say boehmgc, then you
should check that this other package has been installed. Your
``spkg-install`` script should check that it exists, with code
like the following:
::
Something I did on a long boring train ride: remove some of the Debian
cruft left in the scripts. Please review #12470:
http://trac.sagemath.org/sage_trac/ticket/12470
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-de
I'm fairly certain #11881 (which still needs review) will solve the problem.
At least the most common problem.
Has anyone tried the work around I mentioned below?
-Ivan
On Feb 7, 2012, at 8:34 PM, William Stein wrote:
> Hi,
>
> I just got yet another (almost daily now) bug report about our
On 2012-02-07 21:08, William Stein wrote:
> What I'm suggesting is that the script that auto-adds ticket numbers
> should strip the user-added ticket number first, to avoid extensive
> duplication.
If you send me the magic sed/awk/perl/python/whatever script to do this,
I'll happily use it :-)
--
On 2/7/12 3:17 PM, William Stein wrote:
OK, I'm beginning to be convinced Mercurial is kind of lacking
(compared to git) if the only way for 99% of us to use it is to only
use queues.
To be fair, it's more our workflow than mercurial itself. You have pull
requests and things like that with Me
On Tue, Feb 7, 2012 at 12:59 PM, Jason Grout
wrote:
> On 2/7/12 2:46 PM, William Stein wrote:
>>
>> On Tue, Feb 7, 2012 at 12:28 PM, Jason Grout
>> wrote:
>>>
>>> On 2/7/12 2:16 PM, Robert Bradshaw wrote:
On Tue, Feb 7, 2012 at 12:08 PM, William Stein
wrote:
>
>
On Tue, Feb 7, 2012 at 12:59 PM, Jason Grout
wrote:
> On 2/7/12 2:46 PM, William Stein wrote:
>>
>> On Tue, Feb 7, 2012 at 12:28 PM, Jason Grout
>> wrote:
>>>
>>> On 2/7/12 2:16 PM, Robert Bradshaw wrote:
On Tue, Feb 7, 2012 at 12:08 PM, William Stein
wrote:
>
>
On 2/7/12 2:46 PM, William Stein wrote:
On Tue, Feb 7, 2012 at 12:28 PM, Jason Grout
wrote:
On 2/7/12 2:16 PM, Robert Bradshaw wrote:
On Tue, Feb 7, 2012 at 12:08 PM, William Steinwrote:
On Tue, Feb 7, 2012 at 12:00 PM, Simon King
wrote:
Hi William,
On 7 Feb., 20:47, William Stein
On Tue, Feb 7, 2012 at 12:28 PM, Jason Grout
wrote:
> On 2/7/12 2:16 PM, Robert Bradshaw wrote:
>>
>> On Tue, Feb 7, 2012 at 12:08 PM, William Stein wrote:
>>>
>>> On Tue, Feb 7, 2012 at 12:00 PM, Simon King
>>> wrote:
Hi William,
On 7 Feb., 20:47, William Stein wrote:
>
On 2/7/12 2:16 PM, Robert Bradshaw wrote:
On Tue, Feb 7, 2012 at 12:08 PM, William Stein wrote:
On Tue, Feb 7, 2012 at 12:00 PM, Simon King wrote:
Hi William,
On 7 Feb., 20:47, William Stein wrote:
It's important (in fact, critical) that the trac ticket number is
clearly available in the c
On Tue, Feb 7, 2012 at 12:08 PM, William Stein wrote:
> On Tue, Feb 7, 2012 at 12:00 PM, Simon King wrote:
>> Hi William,
>>
>> On 7 Feb., 20:47, William Stein wrote:
>>> It's important (in fact, critical) that the trac ticket number is
>>> clearly available in the commit message. But having it
On Tue, Feb 7, 2012 at 12:00 PM, Simon King wrote:
> Hi William,
>
> On 7 Feb., 20:47, William Stein wrote:
>> It's important (in fact, critical) that the trac ticket number is
>> clearly available in the commit message. But having it twice in two
>> different ways in almost every message seems
Le Tue, 7 Feb 2012 08:38:16 -0800,
William Stein a écrit :
> On Mon, Feb 6, 2012 at 3:42 PM, Dr. David Kirkby
> wrote:
> > On 02/ 6/12 09:09 AM, Jeroen Demeyer wrote:
> >>
> >> On 2012-02-06 09:33, Dr. David Kirkby wrote:
> >>>
> >>> I think trying to replicate autotools would be just silly.
> >
Hi William,
On 7 Feb., 20:47, William Stein wrote:
> It's important (in fact, critical) that the trac ticket number is
> clearly available in the commit message. But having it twice in two
> different ways in almost every message seems a little bit sloppy to
> me.
We were told, by different rel
Hi,
I just did "hg log" and I'm concerned with the way ticket numbers
appear in log messages. Here's the top few in sage-5.0.beta2:
summary: Trac #12396: #12396: these whitespace changes are needed
for the new doctest framework
summary: Trac #12390: trac 12390 -- the documentation for
nu
Hi,
I just got yet another (almost daily now) bug report about our OS X
binaries being complete crap. This time from a Fields Medalist! So
why don't we deal with this?
The traceback he sent me is exactly the same as the one that started
this thread.This is really stupid.
-- William
On Su
On Tue, Feb 7, 2012 at 8:11 AM, javier wrote:
> How about testig for the desired mathematical properties? If this is a
> Gram-Schmidt test, the resulting matrix M should be orthogonal, so we
> can test for M*M.transpose() being the identity matrix (up to
> numerical accuracy). Of course, this type
On 07/02/2012 16:06, Jason Grout wrote:
On 2/7/12 9:55 AM, Marco Streng wrote:
On 07/02/2012 15:43, Jason Grout wrote:
On 2/7/12 9:34 AM, John H Palmieri wrote:
Or as part of the doctest "normalize" G.round(6): multiply by -1 if
the
real part of the (0,0) entry is positive. If it gets too com
On Wednesday, February 8, 2012 12:18:17 AM UTC+8, javier wrote:
>
> Hi Dima,
>
> I didn't know about CodePcgs, thanks for bringing it up!
> This workaround has the disadvantage that one must re-generate the
> groups each time, which is an annoyance I can live with for now I
> guess.
> Is the
On Mon, Feb 6, 2012 at 3:42 PM, Dr. David Kirkby
wrote:
> On 02/ 6/12 09:09 AM, Jeroen Demeyer wrote:
>>
>> On 2012-02-06 09:33, Dr. David Kirkby wrote:
>>>
>>> I think trying to replicate autotools would be just silly.
>>
>> That's what PARI tried and they are probably the spkg with the *most*
>>
Hi Dima,
I didn't know about CodePcgs, thanks for bringing it up!
This workaround has the disadvantage that one must re-generate the
groups each time, which is an annoyance I can live with for now I
guess.
Is there any advantage in saving the CodePcgs rather than the Small
Group Library ID? In you
How about testig for the desired mathematical properties? If this is a
Gram-Schmidt test, the resulting matrix M should be orthogonal, so we
can test for M*M.transpose() being the identity matrix (up to
numerical accuracy). Of course, this type of indirect test should
belong to the test section, no
On 2/7/12 9:55 AM, Marco Streng wrote:
On 07/02/2012 15:43, Jason Grout wrote:
On 2/7/12 9:34 AM, John H Palmieri wrote:
Or as part of the doctest "normalize" G.round(6): multiply by -1 if the
real part of the (0,0) entry is positive. If it gets too complicated,
maybe it should be moved to a TE
On 07/02/2012 15:43, Jason Grout wrote:
On 2/7/12 9:34 AM, John H Palmieri wrote:
Or as part of the doctest "normalize" G.round(6): multiply by -1 if the
real part of the (0,0) entry is positive. If it gets too complicated,
maybe it should be moved to a TESTS block instead of an EXAMPLES block.
On 2/7/12 9:34 AM, John H Palmieri wrote:
Or as part of the doctest "normalize" G.round(6): multiply by -1 if the
real part of the (0,0) entry is positive. If it gets too complicated,
maybe it should be moved to a TESTS block instead of an EXAMPLES block.
I wonder what part of the algorithm lead
On Tuesday, February 7, 2012 2:49:36 AM UTC-8, Jeroen Demeyer wrote:
>
> What is the correct way to "fix" the following doctest failure? Here, G
> is the result of a gram_schmidt() computation, hence the sign shouldn't
> matter mathematically.
>
> sage -t -force_lib devel/sage/sage/matrix/matri
What is the correct way to "fix" the following doctest failure? Here, G
is the result of a gram_schmidt() computation, hence the sign shouldn't
matter mathematically.
sage -t -force_lib devel/sage/sage/matrix/matrix2.pyx
**
File
54 matches
Mail list logo