public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo]some strange problem with sympy
Date: Sun, 17 Oct 2010 18:42:04 -0500	[thread overview]
Message-ID: <1287358931.31425.0@pavilion64> (raw)
In-Reply-To: <201010181039.12889.f.r.bissey@massey.ac.nz> (from f.r.bissey@massey.ac.nz on Sun Oct 17 16:39:12 2010)

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

François,

On 10/17/2010 04:39:12 PM, François Bissey wrote:
> Hi,
> 
> I think I found the root cause of the problem. sympy's setup.py
> has the following line:
> 
> import sympy
> 
> it is the line triggering everything. I don't know if it calls the already
> installed system sympy or the build copy (but I could find out).
> The matter is it is reproducible by just opening a python2.6 shell
> and typing "import sympy" and you will get the same message.
> Try "import mpmath" and you will get the exact same error. This is
> because the problem comes from mpmath and in the case of sympy
> the copy of mpmath that is shipped with it.
> 

Here I get the

KeyError: 'DOT_SAGE'

when I import sympy from a python shell on a machine where sage-4.6.alpha3 is  
installed but not from one where sage-4.5.3 is installed. However,

installs of 4.6.alpha3 and 4.5.3 both exhibit the error when

ebuild sympy-0.6.6.build compile

is issued.

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-10-17 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17 10:27 [gentoo-science] [sage-on-gentoo]some strange problem with sympy François Bissey
2010-10-17 21:39 ` François Bissey
2010-10-17 23:42   ` Steven Trogdon [this message]
2010-10-18  7:54     ` 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=1287358931.31425.0@pavilion64 \
    --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