#13387: Improve MonoDict and TripleDict data structures
----------------------------------+-----------------------------------------
Reporter: nbruin | Owner: Nils Bruin
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.8
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Nils Bruin | Merged in:
Dependencies: #11521, #12313 | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:27 nbruin]:
> You're not giving me much to go on here ... Clearly on that machine
"long int != int", It being an i386, I'd assume "long int" is 32 bits. Is
"int" 16 bits there?
I'm fairly certain both "long int" and "int" are 32 bits. But any of those
words could refer to the Python type "long" or "int".
> Anyway, on pristine 5.8b0 and 5.8b1 I'm finding that this is line 94. So
are you sure the problem comes from the patch here?
Yes, unmerging the patch fixes the problem. In case you wonder, I also
applied #13618 but that's really only about doctests.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13387#comment:28>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
