Thanks ! This would indeed be an explanation.. This means that the ticket needs work..
Le samedi 1 avril 2017 15:51:47 UTC+2, Volker Braun a écrit : > > Whats problematic is that comparison is falling back to memory position in > your patch. > > An integer like 4 is almost certainly allocated earlier than the symbolic > pi; Repeated runs on the same computer are highly likely to end up in the > same memory order but other operating systems / malloc implementations will > differ. > > > > > > On Friday, March 31, 2017 at 9:30:38 PM UTC+2, Frédéric Chapoton wrote: >> >> Hello, >> >> Could please someone with an apple help me debug the ticket >> https://trac.sagemath.org/ticket/22257 (which stands as a current block >> on our long road to python3, and was positive reviewed before it failed on >> apple) >> >> More specifically, >> >> (1) apply the branch, run the tests: >> >> sage -bt --long src/sage/symbolic/expression.pyx >> >> and confirm that it fails on the problematic line RealSet((0, pi),[pi, >> pi],(pi,4)) >> >> (2) could you then tell me the results of >> >> 0 < pi >> >> pi < pi >> >> pi < 4 >> >> please ? I would like to know what exactly is problematic.. >> >> (3) then wrap the 2 calls to richcmp in "src/sage/rings/real_lazy.pyx" >> with bool( ) (those introduced in the ticket branch) and tell me what >> happens to the doctest failure. >> >> Thanks in advance ! >> >> Frederic >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
