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 machi
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 g
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 mi
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 te
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 eve
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
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.
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?
> Be
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
> 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
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 Sa
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/s
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:
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
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
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.
--~--~-
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'
>
>
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 deterministicall
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 wor
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 M
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 deprec
21 matches
Mail list logo
