On Dec 10, 2008, at 11:29 AM, mhampton wrote:
I have been thinking about the booth at the joint meetings, and what
sort of merchandise we should have/give away/sell. I think the top
priority is to have dvds on hand so that people can easily install and
try out sage.
I agree.
So I am
All well via upgrade from 3.2.1 and all tests pass on Suse 64-bit.
Built fine, tests still running on ubuntu 32-bit. (I put my laptop to
sleep and went to bed forgetting that the -tastall was still running.
When I woke it up this morning it just carried on from where it left
off, with only a 9
On Dec 11, 1:57 am, John Cremona [EMAIL PROTECTED] wrote:
Hi John,
All well via upgrade from 3.2.1 and all tests pass on Suse 64-bit.
Yep, I did some build testing and all tests passed for me on 7
different machines, so it looks like so far we have very little to
worry about.
Built fine,
2008/12/11 mabshoff [EMAIL PROTECTED]:
On Dec 11, 1:57 am, John Cremona [EMAIL PROTECTED] wrote:
Hi John,
All well via upgrade from 3.2.1 and all tests pass on Suse 64-bit.
Yep, I did some build testing and all tests passed for me on 7
different machines, so it looks like so far we have
On Dec 11, 2:22 am, John Cremona [EMAIL PROTECTED] wrote:
2008/12/11 mabshoff [EMAIL PROTECTED]:
SNIP
Cool. William was definitely exited about that patch and I am sure he
is happy to review it, too. He mentioned that this is the first open
source implementation of that algorithm that
Thanks for those David - they look great and will appear on walking
randomly soon.
Best Wishes,
Mike
On Dec 10, 1:17 pm, David Joyner [EMAIL PROTECTED] wrote:
On Wed, Dec 10, 2008 at 3:00 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi all
I hope you didn't mind me highlighting your
Thanks very much for the information. It's not my computer, and it
cannot be upgraded until the course is over, so I'm probably out of
luck. I'll write if I get lucky.
I'm not sure you received my link with the config.log, so here it goes
again:
On amd64 ubuntu 8.10, build went fine. This time the tests did not hang
but all was not quite perfect. I got two of these:
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
*** *** Error: TIMED OUT! *** ***
One was for sage -t devel/sage/sage/calculus/wester.py
and the other forsage
On my laptop (32-bit Pentium M running SuSE), upgrading from
3.2.2.alpha0, it builds without complaining. I am running sage -
testall -long at the moment, and so far there are two failures:
- the one from sage/misc/cachefunc.py which happened last time, with
source introspection not working for
Wait a minute, there is actually something funny going on. The upgrade
process hasn't actually upgraded as it should have: the changes to
file matrix2.pyx that I made as part of #4681, which was merged in
this alpha, haven't actually appeared. Even more strangely, if I do
sage -hg changes on that
On Dec 11, 4:22 am, daveloeffler [EMAIL PROTECTED] wrote:
Hi David,
Wait a minute, there is actually something funny going on. The upgrade
process hasn't actually upgraded as it should have: the changes to
file matrix2.pyx that I made as part of #4681, which was merged in
this alpha,
On Dec 11, 3:57 am, David Joyner [EMAIL PROTECTED] wrote:
Hi David,
On amd64 ubuntu 8.10, build went fine. This time the tests did not hang
but all was not quite perfect. I got two of these:
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
*** *** Error: TIMED OUT! *** ***
One was for
On Dec 11, 3:56 am, Pablo Angulo [EMAIL PROTECTED] wrote:
Hi Pablo,
Thanks very much for the information. It's not my computer, and it
cannot be upgraded until the course is over, so I'm probably out of
luck. I'll write if I get lucky.
I'm not sure you received my link with the config.log,
On Dec 10, 2:48 pm, Jaap Spies [EMAIL PROTECTED] wrote:
mabshoff wrote:
Hello folks,
Hi Jaap,
here goes 3.2.2.alpha1, somewhat later than I had hoped. We have about
a week left in the development cycle, so stay tuned for more alphas.
There are a couple must have tickets left for
On Dec 11, 12:26 pm, mabshoff [EMAIL PROTECTED] wrote:
You likely have two heads, i.e. you need to do a merge. That is why it
is highly recommended to upgrade from a clean branch. hg heads
should tell you if you have more than one head and hg merge tip
should get you all the changes
On Dec 11, 4:54 am, mabshoff [EMAIL PROTECTED] wrote:
On Dec 10, 2:48 pm, Jaap Spies [EMAIL PROTECTED] wrote:
mabshoff wrote:
Hello folks,
Hi Jaap,
here goes 3.2.2.alpha1, somewhat later than I had hoped. We have about
a week left in the development cycle, so stay tuned for more
All well on 32-bit Suse except for this, which looks similar to but
not identical to Jaap's. On second thoughts (after pasting it in) it
does look the same as Jaap's, now that the lines wrap differently.
sage -t devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py
On Dec 11, 9:50 am, John Cremona john.crem...@gmail.com wrote:
All well on 32-bit Suse except for this, which looks similar to but
not identical to Jaap's. On second thoughts (after pasting it in) it
does look the same as Jaap's, now that the lines wrap differently.
sage -t
I'm having trouble building the reference manual. Looks like this is
because there is an r missing in sage.calculus.calculus.py, so the
docstring for the minpoly function is encoded wrongly, and latex2html
sees \var{epsilon} and raises an invalid character error on \v.
Seems a bit pointless
On Dec 11, 10:14 am, daveloeffler dave.loeff...@gmail.com wrote:
Hi David,
I'm having trouble building the reference manual. Looks like this is
because there is an r missing in sage.calculus.calculus.py, so the
docstring for the minpoly function is encoded wrongly, and latex2html
sees
I'm also getting problems with the docstrings in sage/misc/hg.py --
the docstrings look fine at first glance, but the parser produces
\begin{itemize}
...
\begin{verbatim}
...
\end{itemize}
...
\end{verbatim}
and latex doesn't like that (quite understandably). I have no idea how
to fix this.
Hello,
I'd have some questions and suggestions about the functions in
polyhedra.py. I attached a patch with some very simple doc and error
handling improvements. Please tell me if it sound useful. (the patch
is against sage 3.2.1, if you prefer me to use a more current version
of polyhedra,
I wanted to install qepcad-1.50, but failed. After
sage -i qepcad-1.50
it told me that readline is missing. So, I installed readline-dev (kubuntu
hardy) and said
sage -i qepcad-1.50
again. This time I get the error below.
Thanks,
Martin
g++
On Dec 11, 2008, at 10:17 AM, mabshoff wrote:
On Dec 11, 10:14 am, daveloeffler dave.loeff...@gmail.com wrote:
Hi David,
I'm having trouble building the reference manual. Looks like this is
because there is an r missing in sage.calculus.calculus.py, so the
docstring for the minpoly
On Dec 11, 10:57 am, daveloeffler dave.loeff...@gmail.com wrote:
I'm also getting problems with the docstrings in sage/misc/hg.py --
the docstrings look fine at first glance, but the parser produces
\begin{itemize}
...
\begin{verbatim}
...
\end{itemize}
...
\end{verbatim}
and latex
On Dec 11, 10:17 am, mabshoff mabsh...@googlemail.com wrote:
On Dec 11, 10:14 am, daveloeffler dave.loeff...@gmail.com wrote:
Hi David,
I'm having trouble building the reference manual. Looks like this is
because there is an r missing in sage.calculus.calculus.py, so the
docstring for
Thanks very much for taking a look at polyhedra.py. I really enjoy
working on it, and I have some research interests in polyhedra, but I
am not a deep expert in the subject and I have been hoping for
constructive criticism and help.
I thought the union command made sense, but I think I
Oh, I forgot one to address one thing: cddlib is used as a seperate
process, and not wrapped, just because of my lack of skills. Since
its a standard component library it should be used in a smarter way, I
just haven't gotten around to learning how. Most of them time I use
it for relatively big
28 matches
Mail list logo
