Hi,
I posted about this to a thread on sage-release about the same problem, but
realised that sage-devel might be the better place for this.
Short answer: PyOpenSSL 0.12 that comes with sagenb seems to be the culprit
(indirectly, because it fails to load and messes up dlopen). Installing
0.13
I have in the meantime tracked this to ComplexIntervalField and
RealIntervalField both overriding __call__ in a way that seems to preempt
usual coercion from working.
Note that CIF(s2) fails, but CIF.coerce(s2) works just fine. It seems that
CIF/RIF just end up calling
ComplexIntervalFieldEleme
On Friday, August 10, 2012 2:04:46 PM UTC+2, ancienthart wrote:
> Any advice on where to locate the egg file for openssl 0.13?
>
`easy_install` manages to find it by itself for me when I just type
`easy_install pyopenssl`. Try http://pypi.python.org/pypi/pyOpenSSL/0.13
for a manual download.
-
On Sunday, August 12, 2012 3:29:16 AM UTC+2, ancienthart wrote:
>
> Daniel, on the old version of sage (5.2 before I replaced pyOpenSSL), when
> I try this, I get:
Hm, right, it keeps 0.12 for me too, I must have tested this after deleting
0.12 from $SAGE_ROOT/local. However `easy_install -U
On Thursday, September 13, 2012 6:43:05 PM UTC+2, Jan Groenewald wrote:
>
>
> Is it clear that the segfault is harmless to your sage session,
> computations, and data?
> Would it be a good idea to go ahead and update the PPA anyway?
>
AFAIK the only reason 5.3 shipped with pyOpenSSL 0.12 was that
