Changes between Version 54 and Version 55 of Plan/Python3


Ignore:
Timestamp:
06/23/2013 08:47:13 PM (16 months ago)
Author:
Julian
Comment:

_twistedpython3.py is gone.

Legend:

Unmodified
Added
Removed
Modified
  • Plan/Python3

    v54 v55  
    1616 
    1717  1. Tests pass under 3.3. 
    18   1. Ported modules were added to list of ported modules - [source:trunk/admin/_twistedpython3.py admin/_twistedpython3.py] 
     18  1. Ported modules were added to list of ported modules in [source:trunk/setup3.py setup3.py] 
    1919  1. No warnings when running using `-3` mode under Python 2.7. 
    2020  1. All non-docstring strings are clearly marked as one of the various string categories (bytes/unicode/identifier/version-dependent). 
     
    112112 
    113113  1. Select a module that needs to be ported (make sure there is a ticket, no one else has started it, etc). 
    114   1. Add the module and its test module(s) to [source:trunk/admin/_twistedpython3.py admin/_twistedpython3.py] 
     114  1. Add the module and its test module(s) to [source:trunk/setup3.py setup3.py] 
    115115  1. Run [source:trunk/admin/run-python3-tests admin/run-python3-tests] 
    116116  1. Fix syntax errors in the test module 
     
    209209=== Documentation === 
    210210 
    211 Documentation potentially requires porting as well.  An individual example (ie, one of the runnable .py files in a ''doc/<project>/examples/'' directory) can be treated much as a module for the purposes of the porting workflow.  One difference, however, is that the example is not added to the list of ported modules in `admin/_twistedpython3.py`. 
     211Documentation potentially requires porting as well.  An individual example (ie, one of the runnable .py files in a ''doc/<project>/examples/'' directory) can be treated much as a module for the purposes of the porting workflow.  One difference, however, is that the example is not added to the list of ported modules in `setup3.py`. 
    212212 
    213213As with the rest of Twisted, the goal for porting documentation should be a version which is compatible with all supported versions of Python (eg, at this time, Python 2.6, Python 2.7, and Python 3.3).