On Saturday, 17 March 2012 08:23:47 UTC+8, Volker Braun wrote:
>
> I see the arm port as complimentary to the sage app. At one point we'll
> probably want to have an optional server that you can run on your device,
> and fall back to sagemath.org otherwise. But the scope of the GSoC
> project
Harald,
this is great news!
On Saturday, 17 March 2012 05:41:08 UTC+8, Harald Schilly wrote:
>
> Hi everyone. Sage got accepted as a mentoring organization for the GSoC
> project.
>
> This means, there will a couple of new students who pop up here and start
> asking about various projects and
On Mar 17, 1:44 am, William Stein wrote:
> On Fri, Mar 16, 2012 at 1:29 PM, vishu goyal wrote:
> > hello sir,
> > I am an first year cse student and know much of basic and egg level
> > maths. Am A eligible for ur project.
>
> Could you please clarify what "egg level maths" is? I'm not famili
Thank you, that's what I thought. I'll do it outside of GSoC anyway though.
--
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.c
I think having physical constants would be great (probably as
attributes of another object, to avoid cluttering the namespace too
much), but there doesn't seem to be near enough meat here for a full
GSoC project.
On Fri, Mar 16, 2012 at 7:53 PM, Eviatar wrote:
> Hello,
>
> I was thinking about do
Hello,
I was thinking about doing a GSoC project this summer. I don't think I
would need too much mentoring since I have already written several patches
for Sage. My idea was to implement physical constants, much like
http://reference.wolfram.com/mathematica/PhysicalConstants/tutorial/PhysicalC
On Mar 16, 5:41 pm, Harald Schilly wrote:
> Hi everyone. Sage got accepted as a mentoring organization for the GSoC
> project.
>
Wonderful! Great, great job on putting the proposal together to all
of you.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe fr
I see the arm port as complimentary to the sage app. At one point we'll
probably want to have an optional server that you can run on your device,
and fall back to sagemath.org otherwise. But the scope of the GSoC project
is to develop the Sage UI, not to port the Sage server. A full arm port is
On Friday, March 16, 2012 11:10:44 PM UTC+1, Christopher Swenson wrote:
>
> … so we wouldn't have a full port of Sage on the device at all.
>
>
yes, and i also think, that this won't have so much benefit at all
(additionally to the ARM vs. x86 architecture problems). I think, a focus
on a good
Oh, my bad. It looks like we intended what you said -- so we wouldn't have
a full port of Sage on the device at all.
--Christopher
On Fri, Mar 16, 2012 at 15:08, Jason Grout wrote:
> On 3/16/12 4:57 PM, Christopher Swenson wrote:
>
>> Hi!
>>
>> I have a little bit of Android and Sage experience
On 3/16/12 4:57 PM, Christopher Swenson wrote:
Hi!
I have a little bit of Android and Sage experience, so I thought I would
give you a tip or two to get started.
I would imagine that the mentors of this project saw this as roughly
four phases:
1. Get up to speed on Android development. This me
Excellent news! I second Harald's call that quality is better than
quantity when it comes to both students and projects. Requiring
potential students to have at least one non-trivial (well written)
submission before selection is a great way of measuring this.
On Fri, Mar 16, 2012 at 2:41 PM, Haral
Congrats on getting picked this year!
--Christopher
On Fri, Mar 16, 2012 at 14:56, Harald Schilly wrote:
> On Fri, Mar 16, 2012 at 22:49, David Roe wrote:
> > People may have been discouraged by our repeated failure to be selected
> in
> > previous years.
>
> yes, i think our goal should be to
Hi!
I have a little bit of Android and Sage experience, so I thought I would
give you a tip or two to get started.
I would imagine that the mentors of this project saw this as roughly four
phases:
1. Get up to speed on Android development. This mean download and
installing the SDK (see http://de
On Fri, Mar 16, 2012 at 22:49, David Roe wrote:
> People may have been discouraged by our repeated failure to be selected in
> previous years.
yes, i think our goal should be to have just a few - but very
promising - projects for the summer. then we can build on that for the
next year. but it's s
Fantastic! I hope that more people will submit ideas. People may have
been discouraged by our repeated failure to be selected in previous years.
And well done Harald.
David
On Fri, Mar 16, 2012 at 17:41, Harald Schilly wrote:
> Hi everyone. Sage got accepted as a mentoring organization for the
Hi everyone. Sage got accepted as a mentoring organization for the GSoC
project.
This means, there will a couple of new students who pop up here and start
asking about various projects and other issues regarding Sage. We have
never been accepted to GSoC before, so we also have to find a way to
Hi,
I resuscitated sage.math.washington.edu. Everything is thus back now,
except that the /scratch disk on sage.math is broken, which is an
unrelated problem. I've thus set /scratch on sage.math to be exactly
the same (NFS mounted) /scratch as we have on geom and mod. It's the
same speed as /
Hello, I am a B.Tech 3rd year student doing Computer Science and
Engineering. I am interested in working for sage -android as my GSoC
project. The idea of an interactive pocket mathematical tool is really
cool. It is true that people require some handy mathematical tool and what
better place th
On Fri, Mar 16, 2012 at 1:29 PM, vishu goyal wrote:
> hello sir,
> I am an first year cse student and know much of basic and egg level
> maths. Am A eligible for ur project.
Could you please clarify what "egg level maths" is? I'm not familiar with it.
-- William
>
> --
> To post to this grou
hello sir,
I am an first year cse student and know much of basic and egg level
maths .Am A eligible for ur project.
--
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, vi
William Stein writes:
> On Fri, Mar 16, 2012 at 7:47 AM, Keshav Kini wrote:
>> "R. Andrew Ohana" writes:
>>> This makes it obvious that I'm against having later versions of sage
>>> be based upon previous versions, however, I am completely for later
>>> versions of sage having all of the commits
On 3/16/12 12:20 PM, Niles Johnson wrote:
Hello all,
I just noticed that the 'fill' option of implicit_plot is broken. The
following example, from the reference manual [1], returns a plot which is
entirely blue, rather than just filling the circle as the documentation claims.
sage:x,y = va
Hello all,
I just noticed that the 'fill' option of implicit_plot is broken. The
following example, from the reference manual [1], returns a plot which is
entirely blue, rather than just filling the circle as the documentation claims.
sage: x,y = var('x,y')sage: f(x,y) = x^2 + y^2 - 2sage: i
On Thu, Mar 15, 2012 at 10:56 AM, Keshav Kini wrote:
> Robert Bradshaw writes:
>> On Thu, Mar 15, 2012 at 3:34 AM, Dima Pasechnik wrote:
>>> On Thursday, 15 March 2012 17:55:31 UTC+8, Jeroen Demeyer wrote:
Okay, I'll think about your suggestion and changing the merger
procedure.
Hi,
I'm currently reviewing John Palmieri's ticket:
#12670: Store lazy import caches in .sage/cache/ rather than in .sage
The (not so critical) problem solved here is that the cache for lazy import is
currently stored in .sage which is polluted by lots of files (one for each
sage-version
On Fri, Mar 16, 2012 at 08:03, Julien Puydt wrote:
> Le vendredi 16 mars, Keshav Kini a écrit:
>
> If a later version contains everything gone in a previous version...
> then how is it not based on it?
In the sense that you state: that a release is just a tag on the
master branch. Or in other wor
Le vendredi 16 mars, Keshav Kini a écrit:
> "R. Andrew Ohana" writes:
> > This makes it obvious that I'm against having later versions of sage
> > be based upon previous versions, however, I am completely for later
> > versions of sage having all of the commits of earlier versions of
> > sage (as
On Fri, Mar 16, 2012 at 7:47 AM, Keshav Kini wrote:
> "R. Andrew Ohana" writes:
>> This makes it obvious that I'm against having later versions of sage
>> be based upon previous versions, however, I am completely for later
>> versions of sage having all of the commits of earlier versions of sage
"R. Andrew Ohana" writes:
> This makes it obvious that I'm against having later versions of sage
> be based upon previous versions, however, I am completely for later
> versions of sage having all of the commits of earlier versions of sage
> (as well as all relative order maintained).
Just to be
On Fri, Mar 16, 2012 at 1:48 AM, Tim Kroeger <> wrote:
> Dear Mr. Stein,
>
> I appreciate the Sage software project and would like to use it in my
> lectures for some demonstration purposes. However, I would like to easily
> enable interested students to re-run the shown examples on their home
> c
On Fri, Mar 16, 2012 at 06:00, Julien Puydt wrote:
>> beta branch: these would be introduced when the release manager has
>> decided to cut off new features from the next release. these would be
>> heavily tested across many platforms until it was determined stable
>> enough for release, at which
> Why make a difference between "beta branch" and "master branch"? I
> don't really see how they could differ in practice.
For the same reason you started releasing 5.0 prealphas while
finishing up 4.8. It makes sense to continue working on closing
various fixes + improvements/features, but you s
Le vendredi 16 mars, R. Andrew Ohana a écrit:
> On Thu, Mar 15, 2012 at 17:59, Julien Puydt
> wrote:
> > Notice that in (1), rel1 might be what is called a "devel release" ;
> > while in (2), that will just be a "stable release" : what is the
> > point of having "devel releases" when your living t
On 2012-03-16 13:50, R. Andrew Ohana wrote:
> master branch: this is where developers should pull from the vast
> majority of the time
>
> beta branch: these would be introduced when the release manager has
> decided to cut off new features from the next release. these would be
> heavily tested ac
On Thu, Mar 15, 2012 at 17:59, Julien Puydt wrote:
> Notice that in (1), rel1 might be what is called a "devel release" ;
> while in (2), that will just be a "stable release" : what is the point
> of having "devel releases" when your living tree is available for all
> to base their work on?
I agr
On 2012-03-16 13:32, Julien Puydt wrote:
> Le vendredi 16 mars, Jeroen Demeyer a écrit:
>> On 2012-03-16 01:59, Julien Puydt wrote:
>>> your living tree
>> which means what?
>
> It's live vs record.
>
> Developers see where you are directly. You review a patch on trac, you
> say: "Ok, it's in!" a
Le vendredi 16 mars, Jeroen Demeyer a écrit:
> On 2012-03-16 01:59, Julien Puydt wrote:
> > your living tree
> which means what?
It's live vs record.
Developers see where you are directly. You review a patch on trac, you
say: "Ok, it's in!" and indeed, it's there. No need to wait for the
next sna
On 16 Mrz., 01:52, Dima Pasechnik wrote:
> Should we invite Linus to do a demo release for us (unless Jeroen objects)?
> /me *hides*
Greg KH has some nice series in his blog about certain kinds of
requests, see
http://www.kroah.com/log/linux/maintainer-06.html
--
To post to this group, sen
In gmane.comp.mathematics.sage.devel, you wrote:
> On 2012-03-16 01:49, Dima Pasechnik wrote:
>> GAP 4.5 is still unreleased, although coming close to being released; I can
>> get you a snapshot.
>> Send me an email then (I can't put an URL in the open here).
> Why not, it's not a secret:
>
> ftp
On 2012-03-16 09:45, Simon King wrote:
> The question is: Is a missing fortran compiler a good reason to build
> all of GCC?
In fact, yes. Because building "just" a Fortran compiler implies that
most of GCC must be built anyway.
--
To post to this group, send an email to sage-devel@googlegroups.
On 2012-03-16 01:49, Dima Pasechnik wrote:
> GAP 4.5 is still unreleased, although coming close to being released; I can
> get you a snapshot.
> Send me an email then (I can't put an URL in the open here).
Why not, it's not a secret:
ftp://ftp.gap-system.org/pub/gap/gap45/beta/
--
To post to t
Hi Leif,
On 16 Mrz., 08:51, leif wrote:
> Really? Compiling GCC 4.6.3 ('make -j4') with C, C++, Fortran, Java
> and LTO enabled took exactly 3 hours on my dual-core Netbook(!) (AMD
> Fusion E-450), plus <4 minutes 'make install'. (Bootstrapped with GCC
> 4.4.3, '-march=native -O3 -g'.)
I have j
On 2012-03-16 09:31, leif wrote:
> Something I suggested years ago ;-) and still looking forward to it...
http://trac.sagemath.org/sage_trac/ticket/12647
--
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...
On Mar 16, 1:29 am, Julien Puydt wrote:
> Le jeudi 15 mars, leif a écrit:
>
> > P.S.: Perhaps the opportunity to introduce yet another Sage
> > environment variable; to be set in ~/.sagerc of course!
>
> -((10^10)!)! because environment variables for everything is bad
> practice.
Like HOME, CC,
On 2012-03-16 01:59, Julien Puydt wrote:
> your living tree
which means what?
--
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
In gmane.comp.mathematics.sage.devel, you wrote:
> Currently the installation of Sage python module (setup.py), built
> when sage-***.spkg is installed, is using twisted.persisted.styles
> to allow class instances to be pickled.
>
> Basically, a duplicate (slightly more efficient, as it is Cython)
> > > I volunteer for opening a ticket and implementing it: this will very
> > > soon save me time!
> >
> > Sounds good to me. I can't figure out when it was introduced, so i don't
> > know why it was introduced, either. Anyone else know?
>
> A quick search on sage-release reveals #10811: "by defa
On Mar 16, 7:20 am, Simon King wrote:
> Hi all,
>
> On 15 Mrz., 14:10, Simon King wrote:
>
> > And now the bad news: Using the above compiler flags, Sage became
> > MASSIVELY slower, by factors of 2 or 3. That's why I interrupted sage -
> > testall after about 54% (there was no error up to that p
Le jeudi 15 mars, Georg S. Weber a écrit:
>
What I would like to point out is :
(1) current situation : I base my work on rel1,
and when I'm happy with it, learn that there is a rel2 which is
rel1+patch1+...+patch100, with seven conflicts, and I should rebase.
(2) a proper source management sys
50 matches
Mail list logo
