Thank you! I can confirm that, after a distclean, building your branch with `SAGE_PYTHON3=yes` gets me to the same point as you describe. The first few issues are fairly simple. I've pushed some coarse fixes for them to
trac u/nbruin/py3_compat (based on your ugly_python3). I consider these more markers for where the problems are than proper fixes, because they probably break py2. The next issue is a TypeError: __str__ returned non-string (type bytes) which happens in the Parent stuff for "rings/infinity.py" somewhere. The problem is clear: we end up with some byte string from what should be a "str". I don't know where, though. Do "cdef str" objects coerce into "object" as a "str" or as a "bytes"? Probably the latter ... this could be painful. -- 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.
