#16088: Python 3 preparation: Py2 vs. Py3 differences in tracebacks
----------------------------+----------------------------
   Reporter:  wluebbe       |            Owner:
       Type:  enhancement   |           Status:  new
   Priority:  major         |        Milestone:  sage-6.2
  Component:  distribution  |         Keywords:  python3
  Merged in:                |          Authors:
  Reviewers:                |  Report Upstream:  N/A
Work issues:                |           Branch:
     Commit:                |     Dependencies:
   Stopgaps:                |
----------------------------+----------------------------
 Tracebacks can look different. For example in
 [[br]]
 Py2
 {{{
 >>> sys.version
 '2.7.5+ (default, Feb 27 2014, 19:37:08) \n[GCC 4.8.1]'
 >>> 1/0
 Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
 ZeroDivisionError: integer division or modulo by zero
 >>>
 }}}
 while in Py3
 {{{
 >>> sys.version
 '3.3.2+ (default, Feb 28 2014, 00:52:16) \n[GCC 4.8.1]'
 >>> 1/0
 Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
 ZeroDivisionError: division by zero
 >>>
 }}}
 The number of effected modules and a suitable approach have to be
 determined.

--
Ticket URL: <http://trac.sagemath.org/ticket/16088>
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to