On 2012-12-28, Nils Bruin <[email protected]> wrote:
> On Dec 28, 2:17 pm, Simon King <[email protected]> wrote:
>> Could that be ZODB related?
>
> My guess is that ZODB data structures are lying around with fields
> that Python 2.7 recognizes as pointers, but which haven't increased
> the refcount. Thus, if GC examines them it may find more pointers than
> explained by the refcount ... ERROR!
The following function call crashes
sage.databases.conway.ConwayPolynomials().has_polynomial(3,2)
and tracing through it, one sees that ZODB is involved:
> /home/simon/SAGE/debug/sage-5.6.beta1/local/lib/python2.7/site-packages/sage/databases/db.py(125)_load_()
124
--> 125 def _load_(self):
126 import BTrees.OOBTree
ipdb>
> /home/simon/SAGE/debug/sage-5.6.beta1/local/lib/python2.7/site-packages/sage/databases/db.py(126)_load_()
125 def _load_(self):
--> 126 import BTrees.OOBTree
127 from ZODB import FileStorage, DB
> What you SHOULD do is investigate on what
> object the assertion fails.
> I'm pretty sure we have to upgrade ZODB. The linked bugreport upstairs
> declares "python 2.7 will be unsupported unless we have a
> breakthrough", and luckily they did have a breakthrough, so 3.10 does
> support 2.7.
>
> ZODB is just a database that gets used (and several instances
> initialized at startup!) by sage.
See above: It *is* involved.
How can I upgrade it? Is there a trac ticket?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
