On Apr 11, 1:01 am, [EMAIL PROTECTED] wrote:
> Also, I'd like to request that people test the notebook in their favorite
> browser. William and I have made some pretty substantial changes; while I
> think we've caught most of the major bugs, we definately haven't caught them
> all. Get alph
No, I forgot to change it back. Use the patch I posted instead, which
changes all the eis_shift_a's back to eis_shift. The p-adics folder
passes sage -t now.
David
On Thu, Apr 10, 2008 at 8:53 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 11, 12:35 am, "David Roe" <[EMAIL PROTECTED]>
+1 for firefox website architecture style
On Apr 10, 12:08 pm, Harald Schilly <[EMAIL PROTECTED]> wrote:
> On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > The right thing to do is to make Sage easier
> > to install.
>
> Yes, of course, I wanted to point out where the problem
Yep, I'm using gcc 4.3.0.
On Apr 10, 11:07 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Apr 11, 5:02 am, Walt <[EMAIL PROTECTED]> wrote:
>
>
>
> > Just got this build error that told me to post it here:
>
> > mpn_extras.o:mpn_extras.c:(.text+0x2630): first defined here
> > collect2: l
On Apr 11, 5:02 am, Walt <[EMAIL PROTECTED]> wrote:
> Just got this build error that told me to post it here:
>
> mpn_extras.o:mpn_extras.c:(.text+0x2630): first defined here
> collect2: ld returned 1 exit status
> make[2]: *** [libflint.so] Error 1
> make[2]: Leaving directory `/home/zarathustr
Just got this build error that told me to post it here:
mpn_extras.o:mpn_extras.c:(.text+0x2630): first defined here
collect2: ld returned 1 exit status
make[2]: *** [libflint.so] Error 1
make[2]: Leaving directory `/home/zarathustra/Download/sage-3.0.alpha3/
spkg/build/flint-1.06.p2/src'
Error b
Ahhh, this helps a lot. I have been needing more cython help, and I
think this will get me about 90% there.
-M. Hampton
On Apr 10, 6:31 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Robert Bradshaw gave a very introductory talk about Cython yesterday
> to my undergraduate
> class, wh
On Apr 11, 12:35 am, "David Roe" <[EMAIL PROTECTED]> wrote:
> I think Willem fixed this bug. I've made the same change a few other
> places and added a doctest.
> David
Hi David,
I posted a one line patch to make you patch compile. It is attached to
#2843. Can you have a look? craigcitro just
I should say, I'm forwarding this code to sage-devel in the hopes that
somebody can
do something to it, since I'm too busy right now.
-- Forwarded message --
From: William Stein <[EMAIL PROTECTED]>
Date: Thu, Apr 10, 2008 at 5:36 PM
Subject: Fwd: tick mark bundle
To: "sage-devel@g
-- Forwarded message --
From: Gerhard Ertaler <[EMAIL PROTECTED]>
Date: Wed, Apr 9, 2008 at 4:56 PM
Subject: tick mark bundle
To: [EMAIL PROTECTED]
The code replaces the _tastefulticks routine
in axes.py without altering the API.
It would be trivial to allow the user to specify
On Thu, Apr 10, 2008 at 4:01 PM, gerhard <[EMAIL PROTECTED]> wrote:
>
> Just to illustrate, the results of something like
> plot(sin(40*x),(1.96,2.04))
> are intriguing
The output in Sage now is just plain crap and totally wrong.
William
--~--~-~--~~~---~--
Hi,
Robert Bradshaw gave a very introductory talk about Cython yesterday
to my undergraduate
class, which I video'd and uploaded to google video here:
http://wiki.wstein.org/2008/480a/schedule/2008-04-09
(The aspect ratio is wrong... sigh, but otherwise the video works fine.)
--
William St
Also, I'd like to request that people test the notebook in their favorite
browser. William and I have made some pretty substantial changes; while I
think we've caught most of the major bugs, we definately haven't caught them
all. Get alpha4, or apply #2869 to alpha3.
http://trac.sagemath.org
Just to illustrate, the results of something like
plot(sin(40*x),(1.96,2.04))
are intriguing
-gerhard
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For
Hello folks,
it has been eleven days since the last stable Sage release and I can
imagine that William is getting jittery for another release. So I
would suggest that interested parties meet in IRC Saturday and/or
Sunday for some final push to get 3.0 ready for release. What needs to
be done?
*
I think Willem fixed this bug. I've made the same change a few other
places and added a doctest.
David
On Mon, Apr 7, 2008 at 11:16 AM, Kiran Kedlaya <[EMAIL PROTECTED]> wrote:
>
> Jen Balakrishnan spent time with some of the usual suspects during the
> Arizona Winter School tracking down bugs
This may be of interest to Sage.
Begin forwarded message:
> From: "Ondrej Certik" <[EMAIL PROTECTED]>
> Date: April 10, 2008 12:36:47 PM PDT
> To: [EMAIL PROTECTED]
> Subject: [soc2008-mentors] SymPy apps -- looking for comments and
> mentors
>
> Hi,
>
> there are 10 applications for SymPy at P
On Apr 10, 2008, at 11:10 AM, Michael.Abshoff wrote:
>
> Brian Granger wrote:
>
> Hi Brian,
>
>>> Sure and it is certainly good to be discussed. I didn't want to be
>>> dismissive about the idea, it is just that I have been in the
>>> "debugging
>>> memory leaks in Cython extension" trenches
Brian Granger wrote:
Hi Brian,
>> Sure and it is certainly good to be discussed. I didn't want to be
>> dismissive about the idea, it is just that I have been in the "debugging
>> memory leaks in Cython extension" trenches for the last eight months and
>> hence I do not trust python or its m
On Apr 10, 2008, at 9:51 AM, Brian Granger wrote:
>
> Hi,
>
> (dual posted to sage and cython)
>
> A few of us (ipython and mpi4py devs) are wondering what the
> best/safest way of allocating dynamic memory in a local scope
> (method/function) is when using cython. An example would be if you
> ne
Brian Granger wrote:
Hi Brian,
>> Well, in the end you end up using sbrk() anyway, but I don't see what is
>> wrong with malloc itself? sage_malloc was introduced a while back to
>> make it possible to switch to a slab allocator like omalloc potentially
>> to see if there is any benefit from
> Sure and it is certainly good to be discussed. I didn't want to be
> dismissive about the idea, it is just that I have been in the "debugging
> memory leaks in Cython extension" trenches for the last eight months and
> hence I do not trust python or its memory management at all any more.
>
William Stein wrote:
> On Thu, Apr 10, 2008 at 10:02 AM, Michael.Abshoff
> <[EMAIL PROTECTED]> wrote:
>> > But, test test suite doesn't test for all of the odd input that users
>> > will feed to sage. These are the cases that will leak memory and
>> > there is not possible way to test for all
> Just for the record, I think Brian isn't suggesting we do anything
> differently with Sage. He's writing lots of _new_ code using
> Cython for his distributed matrix arrays project, and ran into this problem,
> and thought -- surely the Sage folks have solved this. Then he looked
> at our
> Well, in the end you end up using sbrk() anyway, but I don't see what is
> wrong with malloc itself? sage_malloc was introduced a while back to
> make it possible to switch to a slab allocator like omalloc potentially
> to see if there is any benefit from it.
And that makes sense.
> Abso
On Thu, Apr 10, 2008 at 10:02 AM, Michael.Abshoff
<[EMAIL PROTECTED]> wrote:
>
> > But, test test suite doesn't test for all of the odd input that users
> > will feed to sage. These are the cases that will leak memory and
> > there is not possible way to test for all of them. Also debugging
>
On Thu, Apr 10, 2008 at 10:12 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
> > (I'm not on the SAGE list so not dual-posting)
> >
> > > A few of us (ipython and mpi4py devs) are wondering what the
> > > best/safest way of allocating dynamic memory in a local scope
> > > (method/function) is
Brian Granger wrote:
> On Thu, Apr 10, 2008 at 10:27 AM, Michael.Abshoff
> <[EMAIL PROTECTED]> wrote:
>> Brian Granger wrote:
>>
>>> Hi,
>>>
>> Hi Brian,
>>
>>
Hi Brian,
>>
>>> (dual posted to sage and cython)
>>>
>>> A few of us (ipython and mpi4py devs) are wondering what the
>>> best/safest
> It's I think a general problem not only in Python but in programming
> in general. The authors of http://www.flintlib.org/ -- a pure C library --
> spent a lot of time worrying about this, just to I think decide that it's
> a really hard problem.
Very true.
> That said, there is definite
On Thu, Apr 10, 2008 at 10:27 AM, Michael.Abshoff
<[EMAIL PROTECTED]> wrote:
> Brian Granger wrote:
>
> > Hi,
> >
>
> Hi Brian,
>
>
>
> > (dual posted to sage and cython)
> >
> > A few of us (ipython and mpi4py devs) are wondering what the
> > best/safest way of allocating dynamic memory in a loc
On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> The right thing to do is to make Sage easier
> to install.
Yes, of course, I wanted to point out where the problem is and how it
could be handled, the current issue with the Windows install, in my
opinion, is the lack of a nativ
On Thu, Apr 10, 2008 at 10:04 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>
> > > Lisandro Dalcin (author of mpi4py) came up with the following trick
> > > that, while more complicated, prevents memory leaks:
> > >
> > > cdef extern from "Python.h":
> > > object PyString_FromStri
On Thu, Apr 10, 2008 at 9:27 AM, Michael.Abshoff
<[EMAIL PROTECTED]> wrote:
>
> Brian Granger wrote:
> > Hi,
>
> Hi Brian,
>
>
> > (dual posted to sage and cython)
> >
> > A few of us (ipython and mpi4py devs) are wondering what the
> > best/safest way of allocating dynamic memory in a loca
> > Lisandro Dalcin (author of mpi4py) came up with the following trick
> > that, while more complicated, prevents memory leaks:
> >
> > cdef extern from "Python.h":
> > object PyString_FromStringAndSize(char*,Py_ssize_t)
> > char* PyString_AS_STRING(object)
> >
> > cdef inline
Brian Granger wrote:
> Hi,
Hi Brian,
> (dual posted to sage and cython)
>
> A few of us (ipython and mpi4py devs) are wondering what the
> best/safest way of allocating dynamic memory in a local scope
> (method/function) is when using cython. An example would be if you
> need an array of c int
On Thu, Apr 10, 2008 at 9:51 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> (dual posted to sage and cython)
>
> A few of us (ipython and mpi4py devs) are wondering what the
> best/safest way of allocating dynamic memory in a local scope
> (method/function) is when using cython. An
Hi,
(dual posted to sage and cython)
A few of us (ipython and mpi4py devs) are wondering what the
best/safest way of allocating dynamic memory in a local scope
(method/function) is when using cython. An example would be if you
need an array of c ints that is locally scoped.
The big question is
On Thu, Apr 10, 2008 at 9:04 AM, Martin Albrecht
<[EMAIL PROTECTED]> wrote:
>
> > I reckon it needs to be WAY simpler than this. It needs to be a
> > single click from the main page, labelled "Download Sage for
> > Microsoft Windows", which goes straight to a self-extracting
> > installer. The
> I reckon it needs to be WAY simpler than this. It needs to be a
> single click from the main page, labelled "Download Sage for
> Microsoft Windows", which goes straight to a self-extracting
> installer. The contents of README.txt need to be put on the screen
> without even needing to click on RE
On Apr 10, 2008, at 11:35 AM, mabshoff wrote:
> On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
>> We should make Sage as easy or easier to install than
>> any of Mathematica, Maple, Matlab, or Magma.
>> I see no reason to compromise on this at all, since the
>> goal is to prov
On Thu, Apr 10, 2008 at 8:35 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
>
> > We should make Sage as easy or easier to install than
> > any of Mathematica, Maple, Matlab, or Magma.
> > I see no reason to compromise on this
On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> We should make Sage as easy or easier to install than
> any of Mathematica, Maple, Matlab, or Magma.
> I see no reason to compromise on this at all, since the
> goal is to provide a viable alternative to Mathematica,
> Maple, Matl
Dear William,
On Apr 10, 4:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> We should make Sage as easy or easier to install than
> any of Mathematica, Maple, Matlab, or Magma.
This is very reasonable IMO.
Would it be feasible and reasonable to provide several ways of
installations, with bri
> > Incidentally, here are last weeks download numbers on sagemath.org and
> > sage.math.washington.edu (2 of the download sites):
> >
> > Linux Binary: 81
> > OS X Binary: 42
> > Source: 76
> > VMware: 95
> >
> > TOTAL: 294
>
> I agree with all this but really just want to pipe
Tom,
Confirmed working in 3.0.alpha3.
On Apr 9, 10:39 pm, [EMAIL PROTECTED] wrote:
> Try alpha3, and ignore my last email. William and I have been re-working
> js.py quite a bit. As of alpha2, I think you needed to use ctrl-backspace to
> delete a cell. That didn't last long, and backspace
Alpha 3 issues:
On sage.math:
The following tests failed:
sage -t devel/sage/sage/matrix/matrix_generic_dense.pyx # Segfault
sage -t devel/sage/sage/matrix/matrix_mod2_dense.pyx # Segfault
sage -t devel/sage/sage/libs/ntl/ntl_GF2.pyx # Segfault
sage -t devel/
On Thu, Apr 10, 2008 at 10:40 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Thu, Apr 10, 2008 at 6:22 AM, Harald Schilly
> <[EMAIL PROTECTED]> wrote:
> >
> > On Apr 10, 2:14 pm, mhampton <[EMAIL PROTECTED]> wrote:
> >
> > > A link to 7zip.org right by the archive or in the install in
On Thu, Apr 10, 2008 at 6:22 AM, Harald Schilly
<[EMAIL PROTECTED]> wrote:
>
> On Apr 10, 2:14 pm, mhampton <[EMAIL PROTECTED]> wrote:
>
> > A link to 7zip.org right by the archive or in the install instructions
> > would help.
>
> will be there ...
>
>
> > but I'm not convinced that computer
On Apr 10, 2:14 pm, mhampton <[EMAIL PROTECTED]> wrote:
> A link to 7zip.org right by the archive or in the install instructions
> would help.
will be there ...
> but I'm not convinced that computer literacy of any depth
> as increased ...
Yes, especially because I think that's far more genera
Installs fine (ubuntu 7.10 amd64) but has anyone seen something like this:
sage -t devel/sage/sage/gsl/gsl_random.pxi
[2.3 s]
sage -t devel/sage/sage/lfunctions/lcalc.py
Aborted (core dumped)
A mysterious error (perphaps a memory error?) occurred, which may have
crashed doctest.
An anecdote: I have been unable to get 95% of my students to install
sage on their own machines; in at least two cases they got hung up on
7zip and came to me for help. Probably several more got stuck and
didn't come for help. (To be fair: I haven't tried that hard to push
personal installs, sin
I would just like to give a +1 on the importance of fixing this. I am
often irritated by my explicit bounds being expanded in hard to
predict ways. I am somewhat confused by the way the 2D graphics use
and alter matplotlib, so I didn't fix it myself either, but I could at
least review a patch.
On Wednesday 09 April 2008 07:37:56 pm gerhard wrote:
> * The actual bounds used for the axes
>can yield very surprising results.
>Should the range bounds be honored if
>the user sets them explicitely?
Since we had a thread about this a bit ago and I was allegedly going to write
a pa
On Apr 10, 4:29 am, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> It is *341* MB vs. *601* MB,
that's really huge.
> Well, I prefer not to use self extracting executables either,...
Well, I don't see a problem in using a self extracting 7z archive. A
note on the download site with short inst
On Apr 10, 4:18 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> I like the "raise an exception" behavior, because it would eliminate
> questions asking why form1 and form2 below are different (from this
> sage-support
> threadhttp://groups.google.com/group/sage-support/browse_thread/thread/79d0...).
I built alpha3 ok but had two bad fails with --testall:
The following tests failed:
sage -t devel/sage/sage/plot/plot.py # Segfault
sage -t devel/sage/sage/interfaces/psage.py # Segfault
--
BUT when I re-ran t
56 matches
Mail list logo
