Yeah, you should be able to grep out the couple instances of iteritems, that must've slipped through the cracks of the test suite, it shouldn't be too hard to fix manually if you want to do that.
Sean On Nov 30, 2013 5:46 PM, "Sergey B Kirpichev" <[email protected]> wrote: > On Sat, Nov 30, 2013 at 03:37:48PM -0800, Rathmann wrote: > > Well, independent of the architectural issues, this seems like a > > (significant?) regression. The attached file fails (at least for > me) for > > Python3 with a current git build, where it presumably was OK when we > used > > 2to3 on the Python3 version. > > Yes. The worst thing - it's the compatibility.py... > > > What is the best way to fix? Edit the iteritems uses by hand? > > Yes, why not? There seems to be very few remaining > instances of iteritems usage. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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/sympy. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy. For more options, visit https://groups.google.com/groups/opt_out.
