> > Is there a reason why we aren't using six? > It's covering a lot more ground than what compatibility.py does for Python > 2/3 compatibility. >
The gist of it is that while six covers a lot of ground, most of it is ground we don't need covered, and we also do some custom stuff we need [1]. Six supports everything back to 2.4, and we only need to 2.6, which is much more forgiving. The 2/3 lines of code that were added to core/compatibility is ~100 lines, while six comes in at >500. I'd started the codebase conversion using six, but was able to consolidate to a few items once I got things working. Is there anything in particular you needed to do some form of version sniffing outside of core/compatibility? I feel the only explicit 2/3 detection should be done there, and the relevant items imported. Sean [1] https://github.com/sympy/sympy/pull/2318#issuecomment-21565109 -- 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.
