Hello,
I noticed the following discrepancy:
sage: ZZ(RR(3))
3
sage: RR(3) in ZZ
True
sage: ZZ(CC(3, 0))
TypeError: unable to coerce to
an integer
sage: CC(3, 0) in ZZ
False
It's useful in some contexts to be able to recognize integer-like objects,
and it seems that doing x in ZZ is the most co
On Saturday, August 24, 2013 5:35:47 AM UTC-7, Jeroen Demeyer wrote:
>
> In http://trac.sagemath.org/ticket/15045, we noticed a problem with the
> ATLAS build process involving shared libraries. It's a problem which
> doesn't occur often, it happens essentially randomly (but mostly/only on
> AMD
There is a second problem, also, with the use of "verbose" in Cython
code in the sage library. When "verbose" is called, the code for the
verbosity mechanism decides whether to print the message based on the
name of the module containing the calling function. Unfortunately this
introspection mechan
In http://trac.sagemath.org/ticket/15045, we noticed a problem with the
ATLAS build process involving shared libraries. It's a problem which
doesn't occur often, it happens essentially randomly (but mostly/only on
AMD processors). It does not happen with a statically linked ATLAS. It
has been r
When trying to build sage, I came across a weird situation with matplotlib
on OS X.
The setup deemed my default version of gcc (LLVM) to be too old (equivalent
to 4.2) and downloaded GNU GCC 4.6. However, the build script for
matplotlib insisted on having the '-arch' option for compilation via
