[sage-devel] Re: Sage 3.2.alpha0 released
On Mon, Oct 20, 2008 at 09:24:08AM -0700, mabshoff wrote: > > Hello folks, > > here goes Sage 3.2.alpha0. The big new thing is the pynac interface. > Other than that various fixes, features and doctests. Please give it a > try and give feedback. Builds and tests ok here on an amd64 gentoo machine. -Willem Jan --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] insane system call activity.
Hi,
I'm kind of puzzled with sage-3.1.4. When computing within the
interpreter, sage is frantically searching for some .pyx files,
unfortunately to no avail. This occurs even when no attached file is
new. At the end of this mail comes an excerpt of the strace output
(linux 64bit, compiled with gcc 4.3.0).
The most surprising to me is the long search path for an internal
file. Sage should just now where to look, shouldn't it ? Furthermore,
sage doesn't even have in its search path the directories where those
files are placed (/localdisk/sage-3.1.4/devel/sage-main/sage/rings/
integer.pyx in this case)
I tried hard-linking all the .pyx files I could find into one of the
directories of the search path. It reduces of course the length of the
search loops wince they succeed at the first attempt, but searching is
triggered still, at the rate of more than one thousand searches per
second.
Maybe there's something I don't understand here, but at least the
current situation seems rather untidy...
Regards,
E.
stat("integer.pyx", 0x74314c50) = -1 ENOENT (No such file or
directory)
stat("integer.pyx", 0x74314c50) = -1 ENOENT (No such file or
directory)
stat("/localdisk/sage-3.1.4/local/bin/integer.pyx", 0x74314c50) =
-1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
setuptools-0.6c8-py2.5.egg/integer.pyx", 0x74314c50) = -1 ENOTDIR
(Not a directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
SQLAlchemy-0.4.6-py2.5.egg/integer.pyx", 0x74314c50) = -1 ENOENT
(No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
Jinja-1.2-py2.5-linux-x86_64.egg/integer.pyx", 0x74314c50) = -1
ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
Pygments-0.11.1-py2.5.egg/integer.pyx", 0x74314c50) = -1 ENOENT
(No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
Sphinx-0.5dev_20081021-py2.5.egg/integer.pyx", 0x74314c50) = -1
ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/
integer.pyx", 0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/bin/integer.pyx", 0x74314c50) =
-1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python/integer.pyx",
0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python25.zip/integer.pyx",
0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/plat-linux2/
integer.pyx", 0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/lib-tk/integer.pyx",
0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/lib-dynload/
integer.pyx", 0x74314c50) = -1 ENOENT (No such file or directory)
stat("/localdisk/sage-3.1.4/local/lib/python2.5/site-packages/IPython/
Extensions/integer.pyx", 0x74314c50) = -1 ENOENT (No such file or
directory)
stat("/home/manu/.sage/ipython/integer.pyx", 0x74314c50) = -1
ENOENT (No such file or directory)
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [Sage] #4249: [with patch] Inconsistency in number field integral bases
2008/10/20 Willem Jan Palenstijn <[EMAIL PROTECTED]>: > > Hi, > > I traced this down to integral_elements_with_trace not handling the > signs in pari's output of qfminim properly. It will only return a single > element from each pair of conjugates, and depending on > F.reduced_basis(), it might miss elements in ZZ with the required trace > entirely. > > sage: F. = NumberField(x^2-5) > sage: F.integral_elements_with_trace([8.0,12.0]) > [3/2*t + 9/2, t + 5, t + 4, 1/2*t + 11/2, 1/2*t + 9/2, 6, 5, 4] > sage: (-1/2*t + 9/2).trace() > 9 > sage: F.integral_elements_with_trace([8.0,8.0]) > [4] > > On the machine where the doctest failed, I got an empty [] with this > final command. > > Any opinions on if integral_elements_with_trace() should return both > conjugates, or only one? Well done: there is definitely a bug here, since in your example: sage: (t+4).trace() 8 sage: F.integral_elements_with_trace([7.9,8.1]) [] On your second question, I think the user would expect to see all elements with trace in the range, not just one of a set of conjugates, though one might want to add a parameter flag to list only one. Someone will need to fix this and see if the original problem them goes away. Meanwhile I'll add this discussion to the ticket (though perhaps it should be a differetnt icket?) John > > -Willem Jan > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
mabshoff wrote: > Hello folks, > > here goes Sage 3.2.alpha0. The big new thing is the pynac interface. > Other than that various fixes, features and doctests. Please give it a > try and give feedback For a source tarball and a sage.math only > tarball see > On Fedora 9, 32 bits:The following tests failed: sage -t devel/sage/sage/plot/plot.py sage -t devel/sage/sage/algebras/group_algebra.py sage -t devel/sage/sage/algebras/group_algebra.py ** File "/home/jaap/downloads/sage-3.2.alpha0/tmp/group_algebra.py", line 230: sage: OG(FormalSum([ (1, G(2)), (2, RR(0.77)) ]), check=False) Expected: [2 0] [0 2] + 2*0.770 Got: 2*0.770 + [2 0] [0 2] ** 1 items had failures: 1 of 15 in __main__.example_9 ***Test Failed*** 1 failures. For whitespace errors, see the file /home/jaap/downloads/sage-3.2.alpha0/tmp/.doctest_group_algebra.py [9.9 s] exit code: 1024 sage -t devel/sage/sage/plot/plot.py [254.9 s] -- All tests passed! Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Using Pynac variables in plot has problems
The new variables don't seem to work well with the plotting code as
is; I give below output for two plots using old and new variables. I
assume this is known, but just wanted to put it out there.
On the plus side, the new variables are MUCH faster. How do I know?
Because for the first time ever using Sage, I don't have to wait for a
variable! It is also nice to not see that "Exiting spawned Maxima
process." message. So thank you to Burcin and the rest involved in
this.
- kcrisman
Examples:
Using old variables in 3.2.alpha0 works fine:
sage: var('x,y,z')
(x, y, z)
sage: plot(x^2,0,1) [works]
sage: plot(x^2,x,0,1) [works]
Using new variables in same version, not so good:
sage: var('x,y,z', ns=1)
(x, y, z)
sage: (x+y).variables()
[x, y] # proves we have the new variables
sage: plot(x^2,0,1)
verbose 0 (3605: plot.py, _plot) WARNING: When plotting, failed to
evaluate function at 400 points.
verbose 0 (3605: plot.py, _plot) Last error message:
''sage.symbolic.expression.Expression' object is not callable'
sage: plot(x^2,x,0,1)
verbose 0 (3400: plot.py, plot) there were 3 extra arguments (besides
x^2)
---
UnboundLocalError Traceback (most recent call
last)
/Users/.../site-packages/sage/plot/plot.pyc in plot(funcs, *args,
**kwds)
3601 if do_show:
3602 G.show()
-> 3603 return G
3604
3605 def _plot(funcs, xrange, parametric=False,
UnboundLocalError: local variable 'G' referenced before assignment
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Using Pynac variables in plot has problems
On Tue, Oct 21, 2008 at 6:30 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>
> The new variables don't seem to work well with the plotting code as
> is; I give below output for two plots using old and new variables. I
> assume this is known, but just wanted to put it out there.
That's because we have a big todo list for transitioning completely over
to Pynac, and we haven't got to the plotting part yet. I.e., it's really
just not implemented (yet).
William
>
> On the plus side, the new variables are MUCH faster. How do I know?
> Because for the first time ever using Sage, I don't have to wait for a
> variable! It is also nice to not see that "Exiting spawned Maxima
> process." message. So thank you to Burcin and the rest involved in
> this.
>
> - kcrisman
>
> Examples:
>
> Using old variables in 3.2.alpha0 works fine:
> sage: var('x,y,z')
> (x, y, z)
> sage: plot(x^2,0,1) [works]
> sage: plot(x^2,x,0,1) [works]
>
> Using new variables in same version, not so good:
> sage: var('x,y,z', ns=1)
> (x, y, z)
> sage: (x+y).variables()
> [x, y] # proves we have the new variables
> sage: plot(x^2,0,1)
> verbose 0 (3605: plot.py, _plot) WARNING: When plotting, failed to
> evaluate function at 400 points.
> verbose 0 (3605: plot.py, _plot) Last error message:
> ''sage.symbolic.expression.Expression' object is not callable'
> sage: plot(x^2,x,0,1)
> verbose 0 (3400: plot.py, plot) there were 3 extra arguments (besides
> x^2)
> ---
> UnboundLocalError Traceback (most recent call
> last)
>
>
>
> /Users/.../site-packages/sage/plot/plot.pyc in plot(funcs, *args,
> **kwds)
> 3601 if do_show:
> 3602 G.show()
> -> 3603 return G
> 3604
> 3605 def _plot(funcs, xrange, parametric=False,
>
> UnboundLocalError: local variable 'G' referenced before assignment
>
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Using Pynac variables in plot has problems
William Stein wrote:
> On Tue, Oct 21, 2008 at 6:30 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>> The new variables don't seem to work well with the plotting code as
>> is; I give below output for two plots using old and new variables. I
>> assume this is known, but just wanted to put it out there.
>
> That's because we have a big todo list for transitioning completely over
> to Pynac, and we haven't got to the plotting part yet. I.e., it's really
> just not implemented (yet).
>
Can we comment on the todo list? Or is it still at the stage where
people just need to get work done and not worry about lots of
discussion? If we can comment on the todo list, where should we comment
on it?
For example, a very minor nitpick of mine is that var("x,y",ns=1) (the
ns keyword) doesn't make very much sense. I keep trying to remember the
magic "ns" keyword. Of course, when the new variables are default, that
will go away, but that might be a little while longer.
Thanks,
Jason
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Using Pynac variables in plot has problems
kcrisman wrote:
> The new variables don't seem to work well with the plotting code as
> is; I give below output for two plots using old and new variables. I
> assume this is known, but just wanted to put it out there.
>
> On the plus side, the new variables are MUCH faster. How do I know?
> Because for the first time ever using Sage, I don't have to wait for a
> variable! It is also nice to not see that "Exiting spawned Maxima
> process." message. So thank you to Burcin and the rest involved in
> this.
>
> - kcrisman
>
> Examples:
>
> Using old variables in 3.2.alpha0 works fine:
> sage: var('x,y,z')
> (x, y, z)
> sage: plot(x^2,0,1) [works]
> sage: plot(x^2,x,0,1) [works]
>
> Using new variables in same version, not so good:
> sage: var('x,y,z', ns=1)
> (x, y, z)
> sage: (x+y).variables()
> [x, y] # proves we have the new variables
> sage: plot(x^2,0,1)
> verbose 0 (3605: plot.py, _plot) WARNING: When plotting, failed to
> evaluate function at 400 points.
> verbose 0 (3605: plot.py, _plot) Last error message:
> ''sage.symbolic.expression.Expression' object is not callable'
> sage: plot(x^2,x,0,1)
> verbose 0 (3400: plot.py, plot) there were 3 extra arguments (besides
> x^2)
FYI, this is just because the new symbolic expressions are not callable:
sage: expr=x^2
sage: expr(1)
---
TypeError Traceback (most recent call last)
/home/jason/ in ()
TypeError: 'sage.symbolic.expression.Expression' object is not callable
If you wrap it in a python function, for now, you can get the
functionality you want:
sage: expr=x^2
sage: def f(x):
: return expr.subs(x=x)
:
sage: plot(f,0,1)
But I'm sure it'll be taken care of soon anyway.
Jason
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Using Pynac variables in plot has problems
On Tue, Oct 21, 2008 at 7:12 AM, Jason Grout
<[EMAIL PROTECTED]> wrote:
>
> William Stein wrote:
>> On Tue, Oct 21, 2008 at 6:30 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>>> The new variables don't seem to work well with the plotting code as
>>> is; I give below output for two plots using old and new variables. I
>>> assume this is known, but just wanted to put it out there.
>>
>> That's because we have a big todo list for transitioning completely over
>> to Pynac, and we haven't got to the plotting part yet. I.e., it's really
>> just not implemented (yet).
>>
>
>
> Can we comment on the todo list? Or is it still at the stage where
> people just need to get work done and not worry about lots of
> discussion? If we can comment on the todo list, where should we comment
> on it?
It might exist only in our heads :-) But there is actually a file
todo.txt that is here in sage-3.2.*:
devel/sage/sage/symbolic/todo.txt
and it's under revision control. If you looked it over, cleaned
it up a little, thought about what is not listed there but will be
needed in order to fully get rid of the maxima-based symbolic
variables, and submitted a patch (to todo.txt) that would be
very helpful, I think.Well, since Burcin is probably going to
do the work, I hope he agrees with me that this would be
helpful.
-- William
>
> For example, a very minor nitpick of mine is that var("x,y",ns=1) (the
> ns keyword) doesn't make very much sense. I keep trying to remember the
> magic "ns" keyword. Of course, when the new variables are default, that
> will go away, but that might be a little while longer.
>
> Thanks,
>
> Jason
>
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Using Pynac variables in plot has problems
> If you wrap it in a python function, for now, you can get the functionality > you want: > It might exist only in our heads :-) But there is actually a file > todo.txt that is here in sage-3.2.*: > > devel/sage/sage/symbolic/todo.txt > Both answers are very helpful - thanks! - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
Two successful 3.2.alpha0 builds: 1. ubuntu linux gcc 4.2.3 -- all tests pass 2. suse linux gcc 4.1.2 -- still testing Our 64-bit machine has blown another fuse so it's 32-bit only for now... John 2008/10/21 Jaap Spies <[EMAIL PROTECTED]>: > > mabshoff wrote: >> Hello folks, >> >> here goes Sage 3.2.alpha0. The big new thing is the pynac interface. >> Other than that various fixes, features and doctests. Please give it a >> try and give feedback For a source tarball and a sage.math only >> tarball see >> > On Fedora 9, 32 bits:The following tests failed: > > >sage -t devel/sage/sage/plot/plot.py >sage -t devel/sage/sage/algebras/group_algebra.py > sage -t devel/sage/sage/algebras/group_algebra.py > ** > File "/home/jaap/downloads/sage-3.2.alpha0/tmp/group_algebra.py", line 230: > sage: OG(FormalSum([ (1, G(2)), (2, RR(0.77)) ]), check=False) > Expected: > [2 0] > [0 2] + 2*0.770 > Got: > 2*0.770 + [2 0] > [0 2] > ** > 1 items had failures: >1 of 15 in __main__.example_9 > ***Test Failed*** 1 failures. > For whitespace errors, see the file > /home/jaap/downloads/sage-3.2.alpha0/tmp/.doctest_group_algebra.py > [9.9 s] > exit code: 1024 > > > sage -t devel/sage/sage/plot/plot.py > [254.9 s] > > -- > All tests passed! > > > Jaap > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
Hi, Sage3.1.2.alpha0 builds fine on Intel Mac OS X 10.4.11 / Xcode 2.5, make test shows one failure, the same as Jaap Spies already reported: sage -t devel/sage/sage/algebras/group_algebra.py ** File "/Users/georgweber/Public/sage/sage-3.2.alpha0/tmp/ group_algebra.py", line 230: sage: OG(FormalSum([ (1, G(2)), (2, RR(0.77)) ]), check=False) Expected: [2 0] [0 2] + 2*0.770 Got: 2*0.770 + [2 0] [0 2] ** 1 items had failures: 1 of 15 in __main__.example_9 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/georgweber/Public/sage/ sage-3.2.alpha0/tmp/.doctest_group_algebra.py [6.6 s] (The expression is obviously commutative and thus at least mathematically correct, but ...) I did also run make -testlong, and additionally to theat new "group_algebra.py" failure only the two very well known old failures appeared (sr.py, ell_finite_field.py, both havin trac tickets). Cheers, gsw --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
On Oct 20, 2008, at 09:24 , mabshoff wrote: > > Hello folks, > > here goes Sage 3.2.alpha0. The big new thing is the pynac interface. > Other than that various fixes, features and doctests. Please give it a > try and give feedback For a source tarball and a sage.math only > tarball see > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Mac OS X, 10.5.5 (Dual Quad Xeon): built successfully. Testing showed that addition in a group algebra is non-commutative :-} (the same problem in group_algebra.py that others have seen). That was the only failure reported. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds If you're not confused, You're not paying attention --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
All tests passed on amd64 hardy heron. On Mon, Oct 20, 2008 at 12:24 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > here goes Sage 3.2.alpha0. The big new thing is the pynac interface. > Other than that various fixes, features and doctests. Please give it a > try and give feedback For a source tarball and a sage.math only > tarball see > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ > > Cheers, > > Michael > > Merged in Sage 3.2.alpha0: > > #1323: Robert Miller: generate all subspaces of a vector space/ > projective space [Reviewed by David Joyner] > #3872: William Stein, Burcin Erocal: calculus -- incorporate ginac > into Sage [Reviewed by Burcin Erocal, William Stein] > #3920: Martin Albrecht: FiniteFieldElement.vector/matrix -> _vector_/ > _matrix_ [Reviewed by John Palmieri] > #3959: David Loeffler: General group algebras class [Reviewed by David > Joyner] > #3962: Jason Grout: Error in converting vector to SR [Reviewed by > Robert Bradshaw] > #4177: Karl-Dieter Crisman: Put Sage version in Notebook [Reviewed by > John Palmieri] > #4183: Andrzej Giniewicz: ?? can't always find the source for new > style classes [Reviewed by Robert Bradshaw] > #4243: Burcin Erocal: pynac package version bump to 0.1.1 [Reviewed by > Michael Abshoff] > #4244: Burcin Erocal: pynac interface enhancements, symbolic functions > [Reviewed by Mike Hansen] > #4251: David Joyner: typo in installation manual [Reviewed by John > Palmieri] > #4275: Paul Zimmermann: improved doctest for elliptic curves (part 2) > [Reviewed by John Cremona] > #4277: Paul Zimmermann: improve doctest coverage of ell_point.py > [Reviewed by Robert Bradshaw] > #4281: Paul Zimmermann: elliptic curve doctest coverage (part 4) > [Reviewed by John Cremona, Robert Bradshaw] > #4284: Craig Citro: modular symbols -- applying Hecke operator on > cuspidal subspace broken [Reviewed by William Stein] > #4285: Robert Bradshaw: update desolver interface [Reviewed by Paul > Zimmermann, David Joyner] > #4286: Robert Bradshaw: minor improvements to old integer code > [Reviewed by Georg Weber] > #4288: John Cremona: _magma_init_ bug elliptic curve points [Reviewed > by Paul Zimmermann] > #4297: Robert Bradshaw: make sage -cython work on .spyx and library > files [Reviewed by Robert Miller] > #4304: Martin Albrecht: split up NTL's decl.pxi [Reviewed by Robert > Bradshaw, Michael Abshoff] > #4311: Anne Schilling: added documentation for tensor products of > crystals [Reviewed by Mike Hansen] > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Final Sage 3.1.3 sources are out
Hi folks, On Wed, Oct 15, 2008 at 4:04 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > here are the minimal fixes for the final 3.1.3: > > #4271: Paul Zimmermann: improve coverage test of ell_generic.py to > 100%, and fix typos [Reviewed by John Cremona] > #4272: Michael Abshoff: add the files from new coercion to the > reference manual [Reviewed by Mike Hansen] > #4279: Michael Abshoff: Sage 3.1.3.rc0: numerical noise in rings/ > real_lazy.pyx [Reviewed by Mike Hansen] > > Sources and a sage.math binary are at > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.3/ > > The upgrade does not work yet, but hopefully should be done later on > tonight. sage-3.1.3 source distribution was successfully built on MacBook with this architecture: System --- Mac OS X 10.4.8 (8N1430), 32-bit Kernel --- Darwin 8.8.5 Processor --- Intel Core 2 Duo, 2 GHz, 1 GB RAM As with sage-3.1.2, one test failed with a (harmless) timed out error. Other tests passed. Here's some info on the failed test: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [4389.3 s] -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: insane system call activity.
Hmm, it turns out that it's not just any code that triggers this behaviour. However, with the following test case I can reproduce the problem quite deterministically: (term1): strace -p `pidof sage.bin` -e trace='stat' (term2): sage: for i in range(100): float(1)/2 Regards, E. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: insane system call activity.
Hi,
On 21 Okt., 20:59, Emmanuel Thomé <[EMAIL PROTECTED]> wrote:
> Hmm, it turns out that it's not just any code that triggers this
> behaviour. However, with the following test case I can reproduce the
> problem quite deterministically:
>
> (term1): strace -p `pidof sage.bin` -e trace='stat'
>
> (term2):
> sage: for i in range(100): float(1)/2
>
thanks for reporting this issue!
It's a very nice mind teaser to ponder about.
Since I have currently only Mac boxes in my reach, and on Mac OS X,
there does not seem to be neither "strace" nor "pidof", I only can try
to put pure thought on this one.
Firstly, the sage interpreter should not even know about those sage
core *.pyx files!
In the build process, there are corresponding *.so modules (Python so-
called "Extensions")
made out of them, and that is all a
from sage.rings.integer import blahblubber
should care about: it should just use the "integer.so", more
precisely: the file
".../SAGE_ROOT/local/lib/python/site-packages/sage/rings/integer.so"
and then do (python-)internally
"load_dynamically(blahblubber)".
Since you don't complain about "Sage is not working", this seems what
happens anyway in each
of the "thousands searches per second" --- firstly, the *.pyx-file is
searched for, and no matter
how long the search takes or whether it is succesful, the
functionality ("blahblubber") is then gotten from
the *.so file (which has been there all the time, and probably ---
hopefully! --- is searched for
and loaded only once during a Sage/IPython/Python session).
So the question is: what parts of the Sage system *do* know about
*.pyx-files?
It's not the "pure" Python part of Sage.
It's not the IPython interpreter part of Sage.
That leaves in my eyes three possible culprits, that certainly do know
about *.pyx files generally:
a.) the "Cython" package inside python (.../python/site-packages/
Cython/...)
b.) the "pyximport" package inside python (.../python/site-packages/
pyximport/...)
c.) some "sage.misc" module like "interpreter.py" or "preparser.py"
Now if somewhere in the Sage/IPython/Python startup there would be
issued e.g.:
import pyximport
pyximport.install()
I could imagine that the behaviour you desribed would follow from
that:
the "normal" python mechanism to import sth. would have been twisted
in such a way
that every import does a file system access, looking for a *.pyx file
(at least if there is no *.py or *.pyc or *.pyo), and only then
looking internally. or for
a .so-file.
But I admit that I have not come across any clue that "pyximport" is
activated,
nor why that should be.
As for possibility c): these modules seem to be "in action" only if
you load/attach
explicitly some files from the interpreter. But Sage core modules like
"sage.rings.integer"
are built-in, i.e. they are not being interpreted.
Leaves culprit a), i.e. Cython.
But I so far, I only knew that Cython fiddles around with "distutils"
module,
not with the "import" statement.
Well, maybe the "real" Sage developers (I myself have not commited any
code so far)
find some time to investigate.
Cheers,
gsw
> Regards,
>
> E.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: insane system call activity.
On Oct 21, 2008, at 13:26 , Georg S. Weber wrote: > > Hi, > > On 21 Okt., 20:59, Emmanuel Thomé <[EMAIL PROTECTED]> wrote: >> Hmm, it turns out that it's not just any code that triggers this >> behaviour. However, with the following test case I can reproduce the >> problem quite deterministically: >> >> (term1): strace -p `pidof sage.bin` -e trace='stat' >> >> (term2): >> sage: for i in range(100): float(1)/2 >> > > thanks for reporting this issue! > > It's a very nice mind teaser to ponder about. > > Since I have currently only Mac boxes in my reach, and on Mac OS X, > there does not seem to be neither "strace" nor "pidof", I only can try > to put pure thought on this one. FWIW, Mac OS X does have a variety of tools to help with this kind of thing. See, among others, sc_usage (system calls), fs_usage (file- system-specific calls), latency, Shark, and sample/Sample (the capitalized ones are in the Xcode suite - whereever you installed - in various directories under Applications/). Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- I'm beginning to like the cut of his jibberish. --- --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha0 released
It builds fine for me on my MacBook running 10.5.5. Running make test, the only error is the same group_algebra.py error that others have reported. Is it possible to have the make process set a default path when it encounters MacPorts or Fink? The default path is fairly simple, it's just more work on the users part because most people I know that use OS X have one of MacPorts or Fink in their path. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo smime.p7s Description: S/MIME cryptographic signature
[sage-devel] Re: Sage 3.2.alpha0 released
On Oct 21, 2:03 pm, Tim Lahey <[EMAIL PROTECTED]> wrote: > It builds fine for me on my MacBook running 10.5.5. Running make test, > the only error is the same group_algebra.py error that others have > reported. > > Is it possible to have the make process set a default path when it > encounters MacPorts or Fink? The default path is fairly simple, it's > just more work on the users part because most people I know that use > OS X have one of MacPorts or Fink in their path. The plane here is to remove the path where either one of those is installed automatically, but no one has put up code to review yet. > Cheers, > > Tim. Cheers, Michael > > --- > Tim Lahey > PhD Candidate, Systems Design Engineering > University of Waterloo > > smime.p7s > 3KViewDownload --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Legends for 2d plots
I implemented some code to put legends on 2d plots. It currently works, but I would like comments on the interface or better ways to do some things before I put the code up for review in trac. I am aware that the code needs proper documentation, I'll do that tomorrow. Also, should I put a deprecation warning on the label option for plot or is it considered complimentary? Arnaud --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~--- legends.patch Description: Binary data
