Opened 8 years ago

Last modified 2 years ago

#16052 closed enhancement

Meta-ticket for Python 3.3+ preparation (sage library) - stage 2 — at Version 9

Reported by: wluebbe Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: python3 Keywords: python3
Cc: mkoeppe, tscrim Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by wluebbe)

This meta-ticket tracks those tickets for changing the Sage library that did not go into stage 1 (ticket:15980).

Some reasons for assigning tasks to stage 2:

  • The code can run on Python 2 only with the support of imported "compatibility" libraries. [copied from description] Maybe we have to check the licenses of the used compatibility libraries.
  • The tasks are usually more complicated. The approach may not be obvious or uncontroversial.
  • To make progress we need a Python 3.3 test environment for them.

This ticket is referenced by the meta-ticket ticket:15530

No. 2to3 fixer see ticket Comment
2basestring ticket:16064 about 27 modules; details see ticket
5dict ticket:15981 about 227 py modules; details see ticket
7exec ticket:16065 6 modules; details see ticket
8execfile ticket:16066 2 modules; details see ticket
17imports ticket:16069 about 39 modules; details see ticket
22itertools_import ticket:16070 about 12 modules; details see ticket
23itertools ticket:16071 about 20 modules; details see ticket
24long ticket:16072 about 72 modules; details see ticket
25map ticket:16073 about 171 modules; details see ticket (from future_builtins import map ?)
26metaclass ticket:16074 about 30 modules; details see ticket
29next ticket:16075 about 84 modules; details see ticket
30nonzero ticket:16076 about 25 modules; details see ticket
31numliterals ticket:15987 ?? py modules;oct and long literals; details see ticket
36raw_input ticket:16077 3 modules; details see ticket
46unicode ticket:16079 lots of modules?; details see ticket (from __future__ import unicode_literals ?)
47urllib ticket:16080 about 16 modules; details see ticket
49xrange ticket:16081 about 293 modules changes; details see ticket
51zip ticket:16082 about 54 modules; details see ticket (from future_builtins import zip ?)
the following changes do not relate to 2to3
71type() ticket:16085 about 161 modules; different values of type()function; details see ticket
72write() ticket:16086 about 79 modules; in Py3 the write() function has a return value; details see ticket
73traceback ticket:16088 about ?? modules; tracebacks can look different; details see ticket
74file-to-open ticket:16097 about 20 modules; replace builtin file() by open(); details see ticket

Change History (9)

comment:1 Changed 8 years ago by wluebbe

  • Description modified (diff)

comment:2 Changed 8 years ago by wluebbe

  • Description modified (diff)

comment:3 Changed 8 years ago by wluebbe

  • Description modified (diff)

comment:4 Changed 8 years ago by wluebbe

  • Description modified (diff)

Moved ticket:15981 (fix_dict) to stage 2.

comment:5 Changed 8 years ago by wluebbe

  • Description modified (diff)

Moved ticket:15987 (fix_literals) to stage 2.

comment:6 Changed 8 years ago by ppurka

Is it true that this stage 2 depends on the modifications already made to stage 1? Then perhaps we should put #15980 in the dependencies field of the ticket.

comment:7 Changed 8 years ago by wluebbe

  • Description modified (diff)

Stage 2 does not depend on stage 1. The tickets of stage 1 could be solved after stage 2 tickets. They are usually improvements of Py2 code (without relying on separate "compatibility layer").

Both stage 1 and stage 2 are tracked as dependencies of the meta-ticket ticket:15530.

comment:8 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:9 Changed 8 years ago by wluebbe

  • Description modified (diff)

Moved ticket:16067 and ticket:16078 to stage 1 (meta ticket:15980).

Note: See TracTickets for help on using tickets.