I also have a macbook with 10.4.11. I got
sage -t "devel/sage/sage/misc/sagedoc.py"
**
File
"/Users/davidjoyner/sagefiles/sage-4.1.alpha1/devel/sage/sage/misc/sagedoc.py",
line 385:
sage: 'divisors' in _search_src_or_doc('
Marshall,
Please post more details on the following; they are not known:
sage -t "devel/sage/sage/graphs/graph.py"
sage -t "devel/sage/sage/misc/sagedoc.py"
sage -t "devel/sage/sage/parallel/decorate.py"
On Thu, Jun 25, 2009 at 6:27 PM, Marshall Hampton wrote:
>
> I got
Built fine on G4 OSX.4.
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.goo
On 64-bit Fedora 10, I see these doctest failures:
sage -t "devel/sage/doc/fr/tutorial/programming.rst"
sage -t "devel/sage/sage/misc/darwin_utilities.pyx"
Kiran
On Jun 25, 2:18 pm, Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
>
I got the following on an intel mac, 10.4.11, not sure which are known
or unknown issues at this point:
The following tests failed:
sage -t "devel/sage/doc/fr/tutorial/programming.rst"
sage -t "devel/sage/sage/graphs/graph.py"
sage -t "devel/sage/sage/misc/darwin_util
On Jun 25, 11:18 am, Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
> sage.math binary are here:
>
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-s...
>
> If
Maybe we should just bump all the version numbers of python
packages...
I thought this would be a better approach (as did William, who first
suggested it), but I wanted to see if upgrading worked with copying
site-packages first.
--~--~-~--~~~---~--~~
To post to th
These test failures on 32-bit ubuntu (fresh build):
.//home/john/sage-4.1.alpha1/devel/sage/doc/common
.//home/john/sage-4.1.alpha1/devel/sage/doc/en
.//home/john/sage-4.1.alpha1/devel/sage/doc/fr
.//home/john/sage-4.1.alpha1/devel/sage/sage
after these error mess
On Thu, Jun 25, 2009 at 11:21 PM, Tom Boothby wrote:
>
> fails on sage.math, too
Just so you know, upgrading from Python 2.5 to Python 2.6 is really
hard. At a minimum, doing it right should involve rebuilding *every*
Python package in all of Sage. My understanding is that maybe Mike
shortcu
fails on sage.math, too
On Thu, Jun 25, 2009 at 1:56 PM, Jaap Spies wrote:
>
> Robert Miller wrote:
>> This release is primarily the Python upgrade. The source tarball and
>> sage.math binary are here:
>>
>> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar
>> http://sage.ma
Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
> sage.math binary are here:
>
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.ta
Upgrade from 4.0.2 failed (as predicted by the original poster!)
during build of sage.spkg on PPC X.4, with a lot of ImportErrors e.g.
no module named mercurial, no module named jinja (to import from). It
also pulled the outputs of the documentation, which seemed strange to
me (as opposed to buil
Hi folks,
On Fri, Jun 26, 2009 at 4:18 AM, Robert Miller wrote:
>
> This release is primarily the Python upgrade.
The following tickets were merged in Sage 4.1.alpha1:
#6085: Robert Miller: Finish full implementation of c_graphs [Reviewed
by Tom Boothby]
#6359: Mike Hansen: update to Python 2
13 matches
Mail list logo
