On 10 Aug., 07:42, leif wrote:
> I don't know yet if this is again with a *binary* Sage distribution:
>
> http://trac.sagemath.org/sage_trac/ticket/11674
I can reproduce this error with the *binary* Sage 4.7 distribution on
Ubuntu 10.04.3 x86_64 (Core2, Penryn).
Note that it was built on redhawk
Hi,
I'm planning to reboot boxen.math.washington.edu tomorrow morning at
about 10am Pacific Time to see if that helps fix the issues with email
notifications with trac, since so far nobody seems to have had a clue
how to fix them. During this time all sage-related websites, the
notebook server,
I don't know yet if this is again with a *binary* Sage distribution:
http://trac.sagemath.org/sage_trac/ticket/11674
See also
http://trac.sagemath.org/sage_trac/ticket/11581
for a previous one, and also
http://groups.google.com/group/sage-support/browse_thread/thread/4b421d04fb2d2297
[cc'ing
DLMF is a significant upgrade to A&S, but is deeply wedded to a view
of
technology that simply does not accept the notion of symbolic
computation
by computer.
What do I mean by this? I mean that when it comes to computing,
a package either "implements a function" or not. A function is
"implement
On 9 Aug., 22:21, leif wrote:
> On 9 Aug., 22:09, leif wrote:
>
> > On 9 Aug., 16:32, leif wrote:
>
> > > On 9 Aug., 14:00, Jeroen Demeyer wrote:
>
> > > > > See also analogous tickets for other packages:
> > > > > #11661 (gap)
> > > > > #11662 (moin)
> > > > > #11663 (singular)
> > > > > #1166
Am Dienstag, 9. August 2011 16:20:07 UTC+2 schrieb John Cremona:
>
> My guess is the software (which looks very fancy, by the way) just
> doesn't know how to determine the city very well from an IP address.
>
That's true, they certainly just use a simple geolocation resolver and don't
have the re
On 9 Aug., 22:09, leif wrote:
> On 9 Aug., 16:32, leif wrote:
>
> > On 9 Aug., 14:00, Jeroen Demeyer wrote:
>
> > > > See also analogous tickets for other packages:
> > > > #11661 (gap)
> > > > #11662 (moin)
> > > > #11663 (singular)
> > > > #11664 (polybori)
> > > Please review these 4.7.1 bloc
On 9 Aug., 16:32, leif wrote:
> On 9 Aug., 14:00, Jeroen Demeyer wrote:
>
> > > See also analogous tickets for other packages:
> > > #11661 (gap)
> > > #11662 (moin)
> > > #11663 (singular)
> > > #11664 (polybori)
> > Please review these 4.7.1 blockers,
>
> #11663 now has positive review.
Now al
On 9 Aug., 19:27, kcrisman wrote:
> Somehow I don't see NSA posting on sage-devel, though, however useful
> Sage skills would be for working there ;-)
You can be sure they'll at least read it. B-)
And they don't have to post here; they'll contact you.
-leif
--
To post to this group, send an
On Aug 9, 12:55 pm, William Stein wrote:
> On Tue, Aug 9, 2011 at 9:47 AM, Gagan Sekhon wrote:
> > Hello everyone,
> > I just wanted to post a link to current job openings at the company I
> > am currently working at. It is a money transfer company based in San
> > Francisco. It is a wonderful
On 8/9/11 11:58 AM, kcrisman wrote:
(this doesn't count foo.sagenb.org, which have thousands,
cumulatively).
tens of thousands, IIRC. I think sagenb.org now has around 50,000 accounts.
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this grou
> It certainly provides a cheap-shot criticism of Sage to point to the
> lack of a
> windows port. On the other hand, does anyone have a handle on how many
> real people refuse to use Sage because of this?
Not sure, but anecdotally (from conversations devels have had in their
classes, with collea
On Tue, Aug 9, 2011 at 9:47 AM, Gagan Sekhon wrote:
> Hello everyone,
> I just wanted to post a link to current job openings at the company I
> am currently working at. It is a money transfer company based in San
> Francisco. It is a wonderful place to work.
>
> https://www.xoom.com/sendmoneynow/a
Hello everyone,
I just wanted to post a link to current job openings at the company I
am currently working at. It is a money transfer company based in San
Francisco. It is a wonderful place to work.
https://www.xoom.com/sendmoneynow/about/jobs
There are several software engineering positions open
On Aug 9, 7:54 am, kcrisman wrote:
> > I just checked on the Maxima sourceforge page. It seems that between
> > 750-1000 downloads of Windows Maxima per day are registered. I suppose
>
> Certainly right now with the new version. Presumably this counts
> "upgrades"? I do think people tend to u
If they go all the way to a pull request model, this would probably be
a *huge* boon to getting more contributions. I for one would be more
likely to provide patches rather than just reports if I found a bug
(though that won't completely overcome the intrinsic difficulties in
getting into the codeb
On 9 Aug., 16:00, Maarten Derickx wrote:
> Below is the list of current possibilities.
>
> 0. N/A
> 1. Not yet reported upstream; Will do shortly.
> 2. Reported upstream. Little or no feedback.
> 3. Reported upstream. Developers acknowledge bug.
> 4. Reported upstream. Developers deny it's a bug
On Tue, Aug 9, 2011 at 4:43 PM, William Stein wrote:
> On Tue, Aug 9, 2011 at 7:30 AM, John Cremona wrote:
>> There's an interesting article in the August AMS Notices (available
>> here: http://www.ams.org/notices/201107/rtx110700905p.pdf) on the NIST
>> Digital Library, an online + print updatin
On Tue, Aug 9, 2011 at 3:55 PM, John Cremona wrote:
> On Tue, Aug 9, 2011 at 3:43 PM, William Stein wrote:
>> I wonder if there is an official way to petition for the table to be changed?
>>
>
> In the article they say that they would like to be told about
> corrections (I think, I cannot find it
On Tue, Aug 9, 2011 at 3:43 PM, William Stein wrote:
> I wonder if there is an official way to petition for the table to be changed?
>
In the article they say that they would like to be told about
corrections (I think, I cannot find it now). And on the linked page
http://gams.nist.gov/ there is
> I just checked on the Maxima sourceforge page. It seems that between
> 750-1000 downloads of Windows Maxima per day are registered. I suppose
Certainly right now with the new version. Presumably this counts
"upgrades"? I do think people tend to upgrade Sage less often,
because it's such a bi
On Tue, Aug 9, 2011 at 7:30 AM, John Cremona wrote:
> There's an interesting article in the August AMS Notices (available
> here: http://www.ams.org/notices/201107/rtx110700905p.pdf) on the NIST
> Digital Library, an online + print updating of the classic Abramowitz
> & Stegun book. Available her
On 9 Aug., 14:00, Jeroen Demeyer wrote:
> > See also analogous tickets for other packages:
> > #11661 (gap)
> > #11662 (moin)
> > #11663 (singular)
> > #11664 (polybori)
> Please review these 4.7.1 blockers,
Sorry, I did not notice the others were blockers for 4.7.*1* when
changing the subject.
There's an interesting article in the August AMS Notices (available
here: http://www.ams.org/notices/201107/rtx110700905p.pdf) on the NIST
Digital Library, an online + print updating of the classic Abramowitz
& Stegun book. Available here: http://dlmf.nist.gov/
One quote:
"Note: Certain commerci
I just checked on the Maxima sourceforge page. It seems that between
750-1000 downloads of Windows Maxima per day are registered. I suppose
one could add to that the people who download Sage, assuming they get
a copy of Maxima included in the Sage distribution (I assume Sage
downloading doesn't j
On Tue, Aug 9, 2011 at 2:44 PM, Martin Albrecht
wrote:
>> In that summary, Berlin wins the competition for the top non-english
>> speaking city this time ;)
>
> I'm always surprised to see London that high (second highest, right after
> Seattle) on the list. Apparently many people here care about
On 2011-08-09 16:00, Maarten Derickx wrote:
> 1. change: "Reported upstream. Little or no feedback." to "Reported
> upstream. Waiting for reply"
>
> 2. Add a new option: "Reported upstream. Waiting for reply"
>
> I'm slightly in favour for option 1.
+1
I would also shorten "Reported upstream. D
As soon as there is some sort consensus I will change it.
Below is the list of current possibilities.
N/A
Not yet reported upstream; Will do shortly.
Reported upstream. Little or no feedback.
Reported upstream. Developers acknowledge bug.
Reported upstream. Developers deny it's a bug.
Fixed u
On 8/9/11 8:35 AM, Harald Schilly wrote:
Hello everyone
It has been a while since my last update on website statistics. I
don't have much time to give you an in depth analysis, but in general:
not much has changed. If I look back 1 year, the traffic has increased
by about 1/3. That's less than t
> In that summary, Berlin wins the competition for the top non-english
> speaking city this time ;)
I'm always surprised to see London that high (second highest, right after
Seattle) on the list. Apparently many people here care about Sage but I hardly
know any Londoners who are into Sage.
Che
Hello everyone
It has been a while since my last update on website statistics. I
don't have much time to give you an in depth analysis, but in general:
not much has changed. If I look back 1 year, the traffic has increased
by about 1/3. That's less than the year before - I expect that this
slowing
On 9 Aug., 11:12, Simon King wrote:
> On 9 Aug., 09:17, Jeroen Demeyer wrote:
>
> > I actually like "developers deny it's a bug" because it is short and
> > very clear.
>
> "Upstream won't fix it" is short as well, and avoids the association
> of guilt that comes with the word "deny".
Well, "won
On 2011-08-08 15:54, Jeroen Demeyer wrote:
> See also analogous tickets for other packages:
> #11661 (gap)
> #11662 (moin)
> #11663 (singular)
> #11664 (polybori)
I have updated spkgs for these, they all need review. I have built Sage
with these new spkgs and now all files after the Sage build ha
On 9 Aug., 09:17, Jeroen Demeyer wrote:
> I actually like "developers deny it's a bug" because it is short and
> very clear.
"Upstream won't fix it" is short as well, and avoids the association
of guilt that comes with the word "deny".
Best regards,
Simon
--
To post to this group, send an emai
On 2011-08-09 02:34, kcrisman wrote:
> I'd add that the "Developers deny it's a bug" option is at least a
> little offensive, or has the potential to be so. "Developers do not
> view as a bug" or something like that is perhaps a little more
> neutral.
I actually like "developers deny it's a bug"
35 matches
Mail list logo
