Opened 8 years ago

Last modified 2 years ago

#16052 closed enhancement

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

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

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 TBD about 43 changes; details see ticket
7exec TBD about 7 changes; details see ticket
8execfile TBD about 2 changes; details see ticket
10filter TBD about 131 changes; details see ticket
17imports TBD about 128 changes; details see ticket
22itertools_import TBD about 17 changes; details see ticket
23itertools TBD about 37 changes; details see ticket
24long TBD about 136 changes; details see ticket
25map TBD about 496 changes; details see ticket
26metaclass TBD about 45 changes; details see ticket
29next TBD about 232 changes; details see ticket
30nonzero TBD about 30 changes; details see ticket
36raw_input TBD about 6 changes; details see ticket
37reduce TBD about 24 changes; details see ticket
46unicode TBD about ?? changes; to be clarified from __future__ import unicode_literals, details see ticket
47urllib TBD about 41 changes; details see ticket
49xrange TBD about 1,372 changes; details see ticket
51zip TBD about 105 changes; details see ticket

Change History (0)

Note: See TracTickets for help on using tickets.