From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo]mpmath testing
Date: Tue, 19 Oct 2010 15:25:02 -0500 [thread overview]
Message-ID: <1287519902.1572.7@ledaig> (raw)
In-Reply-To: <201010192245.49664.f.r.bissey@massey.ac.nz> (from f.r.bissey@massey.ac.nz on Tue Oct 19 04:45:49 2010)
[-- Attachment #1: Type: text/plain, Size: 2780 bytes --]
On 10/19/10 - 04:45:49, François Bissey wrote:
> Thank you Steve,
>
> Could you send me the result of
> printenv | grep SAGE
> from the machine running sage-4.5.3.
printenv | grep SAGE gives (on _all_ installations)
SAGE_DATA=/usr/share/sage/data
SAGE_BROWSER=/usr/bin/firefox
SAGE_LOCAL=/usr
SAGE_ROOT=/usr/share/sage
SAGE_DOC=/usr/share/sage/devel/sage/doc
For mpmath with sage-4.6alpha3
> I was expecting this error:
> >>> import mpmath
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/lib/python2.6/site-packages/mpmath/__init__.py", line 6,
> in
> <module>
> from ctx_mp import MPContext
> File "/usr/lib/python2.6/site-packages/mpmath/ctx_mp.py", line 48,
> in
> <module>
> from sage.libs.mpmath.ext_main import Context as BaseMPContext
> File "integer.pxd", line 9, in init sage.libs.mpmath.ext_main
> (sage/libs/mpmath/ext_main.c:22894)
> File "integer.pyx", line 165, in init sage.rings.integer
> (sage/rings/integer.c:33926)
> File "/usr/lib/python2.6/site-packages/sage/rings/infinity.py",
> line 200, in
> <module>
> import sage.rings.rational
> File "rational.pyx", line 70, in init sage.rings.rational
> (sage/rings/rational.c:25264)
> File "real_mpfr.pyx", line 1, in init sage.rings.real_mpfr
> (sage/rings/real_mpfr.c:31325)
> File "complex_number.pxd", line 8, in init sage.libs.mpmath.utils
> (sage/libs/mpmath/utils.c:7374)
> File "complex_double.pxd", line 13, in init
> sage.rings.complex_number
> (sage/rings/complex_number.c:18312)
> File "complex_double.pyx", line 95, in init
> sage.rings.complex_double
> (sage/rings/complex_double.c:16534)
> File
> "/usr/lib/python2.6/site-packages/sage/rings/complex_field.py", line
> 89,
> in ComplexField
> C = ComplexField_class(prec)
> File
> "/usr/lib/python2.6/site-packages/sage/rings/complex_field.py", line
> 187, in __init__
> ParentWithGens.__init__(self, self._real_field(), ('I',), False,
> category =
> Fields())
> File
> "/usr/lib/python2.6/site-packages/sage/rings/complex_field.py", line
> 240, in _real_field
> self.__real_field = real_mpfr.RealField(self._prec)
> File "real_mpfr.pyx", line 267, in sage.rings.real_mpfr.RealField
> (sage/rings/real_mpfr.c:4222)
> TypeError: 'NoneType' object is unsubscriptable
> >
>
> ----------------
> I posted about it on the sage-release, where we talk about the
> sage-4.6 pre
> releases, and no one else has the problem so far. If you don't have
> it either
> that may be a problem on my machine.
>
> Francois
>
I don't get the above with an import of mpmath. Just a thought, could
it be mpfr-related. I'm using
mpfr-2.4.2_p3 here.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-10-19 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 11:47 [gentoo-science] [sage-on-gentoo]mpmath testing François Bissey
2010-10-18 15:16 ` Steven Trogdon
2010-10-19 9:45 ` François Bissey
2010-10-19 20:25 ` Steven Trogdon [this message]
2010-10-19 20:41 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1287519902.1572.7@ledaig \
--to=strogdon@d.umn.edu \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox