#15980: Meta-ticket for Python 3.3+ preparation (sage library) - stage 1
--------------------------------+------------------------
       Reporter:  wluebbe       |        Owner:
           Type:  enhancement   |       Status:  new
       Priority:  major         |    Milestone:  sage-6.2
      Component:  distribution  |   Resolution:
       Keywords:  python3       |    Merged in:
        Authors:                |    Reviewers:
Report Upstream:  N/A           |  Work issues:
         Branch:                |       Commit:
   Dependencies:                |     Stopgaps:
--------------------------------+------------------------

Comment (by ohanar):

 Hi Wilfred,

 There is currently a meta-ticket pertaining to supporting Python 3.3 for
 the Sage distribution, which includes making various changes to the build
 system and upgrading various dependencies (see #15530). I've added this
 meta-ticket to that meta-ticket and changed the summary of this one to
 better reflect that it is specifically referring to the sage library.

 I'm a little confused on your distinction between stage 1 and stage 2.
 What exactly are things that go into stage 2 but not into stage 1?

 I don't see anywhere in this list issues with renamed/reorganized
 libraries like urllib or StringIO, maybe this is part of the compatibility
 library that you mention as part of stage 2? Also, probably the biggest
 issue with Python 3 support is the requirement for rich comparison, which
 again wasn't mentioned in here.

--
Ticket URL: <http://trac.sagemath.org/ticket/15980#comment:4>
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