Hi Michael,
On Wed, Apr 22, 2009 at 5:09 PM, mabshoff wrote:
>
> Hi folks,
>
> it would be good if you contributed a feature to Sage 3.4.1 to check
> the release tour at
>
> http://wiki.sagemath.org/sage-3.4.1
>
> and edit what is there already in case it can be improved or add
> something in
On Apr 22, 2009, at 5:13 PM, root wrote:
>
>>> It's on our list too, so it will happen eventually. We definitely
>>> still need to improve our algorithms a lot, see e.g.:
>>>
>>> http://groups.google.com/group/sympy/browse_thread/thread/58916fb31e1ff1ea
>>>
>>> but a nice thing is that it's in P
Hello,
while there should be a quick 3.4.2 to mop up patches from trac before
the big 4.0 jump today we had a planning session during the UW status
meeting about the goals for Sage 4.0. The result is at
http://wiki.sagemath.org/plan/sage-4.0
It still needs a little polish, i.e. the issues fo
> > It's on our list too, so it will happen eventually. We definitely
> > still need to improve our algorithms a lot, see e.g.:
> >
> > http://groups.google.com/group/sympy/browse_thread/thread/58916fb31e1ff1ea
> >
> > but a nice thing is that it's in Python, so it's easy to work with.
> >
> > Ond
Hi Marshall. I think I have a fix for this. But I've started a thread
on the MPIR development list for this:
http://groups.google.co.uk/group/mpir-devel/browse_thread/thread/34a4e60f556c8ba3
Bill.
On 22 Apr, 23:31, Marshall Hampton wrote:
> I am having an error in building 3.4.1 on an intel ma
On Apr 20, 8:15 pm, Jason Grout wrote:
> In addition to the python summer of code projects, here are some other
> projects that may be interesting to Sage developers:
>
> * Scilab applications, including one that replaces maxima with a
> ginac-based symbolic system, another that explores moving
On Wed, Apr 22, 2009 at 7:03 PM, Carl Witty wrote:
>
>
> Couldn't you just pick random values for all of the symbolic constants, as
> well?
Yes, but over what range? If you do that, you've just ensured that it
is correct for
those points. It also could get expensive if you have multiple
constan
On Wed, Apr 22, 2009 at 3:59 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 6:54 PM, Carl Witty wrote:
>>
>>
>> Would it be better to test the results numerically? (For instance,
>> evaluate the integral returned and the desired result at 100 random
>> points to high precision, and ensure tha
On Wed, Apr 22, 2009 at 6:54 PM, Carl Witty wrote:
>
>
> Would it be better to test the results numerically? (For instance,
> evaluate the integral returned and the desired result at 100 random
> points to high precision, and ensure that the relative error between
> the answers at each point is
On Wed, Apr 22, 2009 at 3:35 PM, Tim Lahey wrote:
> The problem arises with all the different integration systems. Usually some
> kind of simplification is needed on the integral returned, even if there
> aren't
> multiple solutions. This complicates the testing procedure since the steps to
> pe
On Wed, Apr 22, 2009 at 3:35 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 6:31 PM, Ondrej Certik wrote:
>>
>>
>> I think sympy will do very poorly if the assumptions are needed, we
>> are still working on the assumptions.
>>
>> So if it turns out too difficult, just skip sympy for the time b
On Wed, Apr 22, 2009 at 6:31 PM, Ondrej Certik wrote:
>
>
> I think sympy will do very poorly if the assumptions are needed, we
> are still working on the assumptions.
>
> So if it turns out too difficult, just skip sympy for the time being,
> we'll get back to it later.
>
The problem arises wit
I am having an error in building 3.4.1 on an intel mac running 10.5.
The error is in mpir:
Deleting assembly files which depend on PIC assembly working or 32 bit
OSX on Intel hardware
checking build system type... Invalid configuration `penryn-apple-
darwin9.6.0': machine `penryn-apple' not recog
On Wed, Apr 22, 2009 at 3:27 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 6:11 PM, Ondrej Certik wrote:
>>
>>
>> We use py.test/nosetest compatible tests, but if you prefer Sage like
>> doctests, that's fine too.
>
> Good to know. I'm not actually using any unit test classes at the moment
>
On Wed, Apr 22, 2009 at 6:11 PM, Ondrej Certik wrote:
>
>
> We use py.test/nosetest compatible tests, but if you prefer Sage like
> doctests, that's fine too.
Good to know. I'm not actually using any unit test classes at the moment
since I have the difficulty that each test has different steps t
On Wed, Apr 22, 2009 at 2:53 PM, Maurizio wrote:
>
>> We managed to get one gsoc project that does the assumptions right, so
>> it may happen anyways over the summer, in fact I very much hope so.
>>
>
> How does assumptions affect this? If that's so important, you should
> probably get a lot of f
On Wed, Apr 22, 2009 at 1:12 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 4:10 PM, Ondrej Certik wrote:
>>
>>
>> It's on our list too, so it will happen eventually. We definitely
>> still need to improve our algorithms a lot, see e.g.:
>>
>> http://groups.google.com/group/sympy/browse_thread
> We managed to get one gsoc project that does the assumptions right, so
> it may happen anyways over the summer, in fact I very much hope so.
>
How does assumptions affect this? If that's so important, you should
probably get a lot of focus on that! But consider also PDE
important ;)
>
> We'll s
On Apr 22, 12:52 pm, Nick Alexander wrote:
> >> To override this in Firefox on Linux, I put
>
> >> #content.ticket { width: 100% !important; }
>
> > Hmm, that seems to be a worthwhile change to me since these days most
> > people should not be limited by 800x600 displays any more? Is anyone
> >
On Apr 22, 1:50 pm, mabshoff wrote:
> On Apr 22, 12:54 pm, "David M. Monarres" wrote:
>
> Hi David,
> The other two failures are upgrade specific and happen when when left
> over pyc and so files are around due to the Quaternion classes being
> moved. One brutal fix is to do delete devel/s
On Apr 22, 12:54 pm, "David M. Monarres" wrote:
Hi David,
> On an upgrade from 3.4 on Mac OS X 10.5.6 (intel) I get the following
> doctest errors:
Thanks for the build report.
> The following tests failed:
>
> sage -t "devel/sage/sage/algebras/quaternion_algebra_element.py"
>
On Wed, Apr 22, 2009 at 4:10 PM, Ondrej Certik wrote:
>
>
> It's on our list too, so it will happen eventually. We definitely
> still need to improve our algorithms a lot, see e.g.:
>
> http://groups.google.com/group/sympy/browse_thread/thread/58916fb31e1ff1ea
>
> but a nice thing is that it's in
On Wed, Apr 22, 2009 at 12:43 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 1:29 PM, root wrote:
>>
>>
>> There is an integration test suite at:
>> http://axiom-developer.org/axiom-website/CATS
>> which has the Schaums integral series along with examples.
>> Each integral result is subtracted
On an upgrade from 3.4 on Mac OS X 10.5.6 (intel) I get the following
doctest errors:
The following tests failed:
sage -t "devel/sage/sage/algebras/quaternion_algebra_element.py"
sage -t "devel/sage/sage/schemes/elliptic_curves/
ell_rational_field.py"
sage -t "deve
>> To override this in Firefox on Linux, I put
>>
>> #content.ticket { width: 100% !important; }
>
> Hmm, that seems to be a worthwhile change to me since these days most
> people should not be limited by 800x600 displays any more? Is anyone
> opposed to this change for some reason?
+1.
Nick
--
On Wed, Apr 22, 2009 at 1:29 PM, root wrote:
>
>
> There is an integration test suite at:
> http://axiom-developer.org/axiom-website/CATS
> which has the Schaums integral series along with examples.
> Each integral result is subtracted from the Schaums answer
> and then simplified, hopefully to a
> >>> Kudos to SymPy!
> >>>
> >>> I'm wondering why the python integration algorithms implemented there
> >>> aren't in the short term adopted by SAGE.
> >>
> >> They are --- you can use them from sympy inside Sage. It's my goal
> >> that all sympy features are nicely integrated in Sage. I work on
On Apr 22, 2009, at 8:38 AM, Ondrej Certik wrote:
>
> On Mon, Apr 20, 2009 at 8:15 PM, Jason Grout
> wrote:
>>
>> In addition to the python summer of code projects, here are some
>> other
>> projects that may be interesting to Sage developers:
>>
>> * Scilab applications, including one that re
On Apr 21, 11:44 am, Pat LeSmithe wrote:
Hi Pat,
> Sage trac's stylesheet sets the width of a ticket's description, change
> history, etc., to 700 pixels:
>
> http://trac.sagemath.org/sage_trac/chrome/common/css/ticket.css
>
> contains
>
> #content.ticket { width: 700px; max-width: 100% }
>
>
>From the point of view of packaging Sage for distributions, having Sage
able to use GMP rather than MPIR is a win, since it means packaging Sage
would not require adding MPIR to the distribution (adding MPIR is one of
the blockers for packaging a more recent Sage in Debian).
-Tim Abbo
On Tue, Apr 21, 2009 at 8:44 PM, Pat LeSmithe wrote:
> Besides username, and
>
> [diff]
> git = true
>
> for binary patches, are there other useful bits I should put in ~/.hgrc?
I have these bits to turn on Mercurial queues (not enabled by default
in Debian) and colordiff (install on Debian/Ubu
Hi folks,
it would be good if you contributed a feature to Sage 3.4.1 to check
the release tour at
http://wiki.sagemath.org/sage-3.4.1
and edit what is there already in case it can be improved or add
something in case it is missing.
Minh: You seem to list both author[s] and reviewer[s] for
On Apr 22, 8:09 am, William Stein wrote:
> On Wed, Apr 22, 2009 at 6:10 AM, Flavio Coelho wrote:
>
> > Hi,
>
> > is it too late to include the multiprocessing package into sage
> > 3.4.1?
>
> No, since we included it in Sage a year ago:
While we ship pyprocessing we should really consider upg
On Wed, Apr 22, 2009 at 9:08 AM, Ondrej Certik wrote:
> welcome competition, because that's the only way to actually move
> forward, but for Sage and sympy. For example thanks to sympy, you
but -> both
O.
--~--~-~--~~~---~--~~
To post to this group, send email t
On Tue, Apr 21, 2009 at 12:44 AM, mabshoff wrote:
>
>
>
> On Apr 21, 12:32 am, Robert Bradshaw
> wrote:
>> On Apr 20, 2009, at 11:44 PM, Maurizio wrote:
>>
>> > Hi Michael,
>>
>> > Actually, I thought that this discussion (especially people much more
>> > expert than me) has clarified the point
On Mon, Apr 20, 2009 at 8:15 PM, Jason Grout
wrote:
>
> In addition to the python summer of code projects, here are some other
> projects that may be interesting to Sage developers:
>
> * Scilab applications, including one that replaces maxima with a
> ginac-based symbolic system, another that ex
On Wed, Apr 22, 2009 at 6:10 AM, Flavio Coelho wrote:
>
> Hi,
>
> is it too late to include the multiprocessing package into sage
> 3.4.1?
No, since we included it in Sage a year ago:
teragon:~ wstein$ sage
--
| Sage Version 3.
On Tue, Apr 21, 2009 at 9:38 AM, dmharvey wrote:
>
> Hi folks,
>
> I have made a basic spkg for GMP 4.3.0:
>
> http://sage.math.washington.edu/home/dmharvey/gmp-4.3.0.spkg
>
> I've only tested on a linux opteron system. It builds fine; there are
> various doctest failures that look related to non
Hi,
is it too late to include the multiprocessing package into sage
3.4.1?
There is a backport of it for python 2.5 in Pypi, which is maintained
by the author of the one which figures in the standard library from
2.6 on.
thanks,
Flávio
--~--~-~--~~~---~--~~
To p
You are always going to be welcome. I always feel like a Johnny come
lately with regard to Sage, even though I started contributing to Sage
with my qsieve about 2.5 years ago. In contrast, you were there, right
in the guts of the thing, right from the start! Your contribution has
always been, and
On Wed, Apr 22, 2009 at 6:22 AM, David Harvey wrote:
>
> Oh look, I've been involved in Sage since mid-2006. This is the first
> major strategic decision with which I've disagreed so strongly, and
> the first time I've felt truly unwelcome on this list. It's quite
> depressing.
>
> I sincerely be
2009/4/22 David Harvey :
>
> Oh look, I've been involved in Sage since mid-2006. This is the first
> major strategic decision with which I've disagreed so strongly, and
> the first time I've felt truly unwelcome on this list. It's quite
> depressing.
>
Of course you are not unwelcome on this list
Oh look, I've been involved in Sage since mid-2006. This is the first
major strategic decision with which I've disagreed so strongly, and
the first time I've felt truly unwelcome on this list. It's quite
depressing.
I sincerely believe the costs of the fork to the community outweigh
the benefits.
2009/4/22 Georg S. Weber :
>
> I have on my to-do-list for a long time now the task to introduce
> canonical choices for e.g. P1List and for bases of modular symbol
> spaces. It would help a lot when interfacing with C libraries that do
> certain calculations very fast, e.g. the set of Heilbronn
Hi all,
On 22 Apr., 06:45, William Stein wrote:
> 2009/4/21 David Harvey :
>
>
>
> > On Apr 21, 2:31 pm, Bill Hart wrote:
>
> >> In some cases it would be less work to just contribute features
> >> directly to MPIR to bring the current code up to par.
>
> > I think you are underestimating how m
On Tue, Apr 14, 2009 at 1:12 AM, William Stein wrote:
>
> On Mon, Apr 13, 2009 at 4:47 PM, David Joyner wrote:
>>
>> On Mon, Apr 13, 2009 at 7:26 PM, Nick Alexander
>> wrote:
>>>
>>>
>>> On 13-Apr-09, at 4:17 PM, David Joyner wrote:
>>>
I don't know if this comment is relevant or not
On Mon, Apr 13, 2009 at 7:26 PM, Nick Alexander wrote:
>
>
> On 13-Apr-09, at 4:17 PM, David Joyner wrote:
>
>>
>> I don't know if this comment is relevant or not to this thread or not
>> but I use the "Discard&quit" button *very* frequently. I tell my
>> students
>> to log into the local Sage se
I apologise if this seemed rude. I should have made the point more
subtly. I'm just trying to deal with it in an open way. David has
taken clear exception to the use of MPIR in Sage by default, and some
of his points are valid for the time being.
But I want to be clear that MPIR is not going
This is precisely why we deprecated all the is_*() functions for end-user use:
--
| Sage Version 3.4.1.rc4, Release Date: 2009-04-19 |
| Type notebook() for the GUI, and license() for information.|
-
In my experience (using emacs which puts tabs in) there has never been
a problem in .py files, but .pyx files would fail to build unless I
use the emacs "untabify" command before rebuilding a file I have
edited.
John
2009/4/22 mabshoff :
>
> Hello folks,
>
> up to now the rules on tabs in Sage l
This is about http://trac.sagemath.org/sage_trac/ticket/3167
If I open a new worksheet and execute
x,y=var('x,y')
plot3d(sin(x*y),(x,-4,4),(y,-4,4))
I see this in Opera's Java Console:
Jmol applet jmolApplet1__319875117923755__ destroyed
Jmol applet jmolApplet2__319875117923755__ initializing
On Apr 21, 2009, at 10:54 PM, Craig Citro wrote:
>> In module sage.rings.integer
>>
>> is_Integer(3/2+1/2)
>>
>> returns
>>
>> False The expected output should be True as 3/2+1/2 = 2.
>>
>> I was planning to use this function to check if the result of
>> division
>> is a whole number.
>>
>
>
52 matches
Mail list logo
