Python 3 porting team

Usertags

Bugs related to this project have usertags applied to them to help track the progress of this task that crosses over many different packages (more about usertags).

Py3 Porting Project bug list

user

usertag

what it means

py3porters-devel@lists.alioth.debian.org

patchme-python3

upstream supports py3k, but we don't ship the deb

py3porters-devel@lists.alioth.debian.org

port-python3

project needs help porting to py3k

py3porters-devel@lists.alioth.debian.org

python3-patch-suggested

A patch to port the project to py3k has been suggested in the BTS

To apply the usertags to a new bug, add the following fields to the pseudo-header (the section at the top of the report body):

User: py3porters-devel@lists.alioth.debian.org
Usertags: patchme-python3

To apply the usertags to existing bugs, use the bts command from the devscripts package:

bts user 'py3porters-devel@lists.alioth.debian.org' , usertags 999999 patchme-python3

where 999999 is the bug number.

The normal tags that the bug tracker uses can also be applied to the bugs. The particularly relevant ones and what they would mean in the context of the Python 3 porting project are:

patch

a patch to add Python 3 support is attached to the bug

help

the porting looks particularly complicated and the maintainer would like assistance

newcomer

the porting looks particularly easy and would be suitable for a new contributor

fixed-upstream

the porting work is done in a new upstream release

wontfix

bug will not be fixed: hopefully we don't see any of these!

Who is working on what?

Project

Porter(s) name on ML / IRC

Workspace

Status

Comment

Depends on (only packages that are not yet py3 ready)

piuparts

Bernhard Janetzki (ierror)

github.com/ierror/piuparts/ierror/piuparts

ongoing

 

python-debianbts

reportbug

tbd

tbd

-

 

python-debianbts

debianmemberportfolio

Jan Dittberner

-

implemented

ported from Pylons to Flask in development branch, deployment pending

 

snapshot.debian.org

Matt Singleton (xcolour), Justin Ryan (justizin)

SnapshotToFlask

planning

Porting to Flask

 

python-debianbts

Bernhard Janetzki (tbd)

tbd

first contact to pkg maintainer via ML

 

a py 3 soap client

python-rpy2

 

ssh://git.debian.org/git/collab-maint/pkg-rpy2.git/

 

 

 

dput

BenFinney (bignose)

https://anonscm.debian.org/git/users/bignose/debian-full/dput.git/

released

 

 

dput-ng

Daniele Tricoli (eriol)

github.com/eriol/dput-ng/tree/py3-port

ongoing

 

 

Resources for new folks

Mailing list

py3porters-devel

IRC Channels

These are on irc.oftc.net (not Freenode, sorry!)

Channel

What help to ask for

#debian-mentors

Help building packages, testing debs, using the bug tracker, whatever

#debian-python

Help with the Debian Python ecosystem, and/or discuss Python 3 porting issues

Debian Bug Tracking System

Debian's bug tracking system keeps up with all the bugs in the 46k binary packages (23k source packages) and handles both synchronous and asynchronous querying both within a package and across packages. For more information on the BTS, including how to manipulate the metadata of the bugs, see the BTS documentation.

The easiest way to report a bug (and include your porting patches) is with the reportbug tool -- that is the reportbug command from the reportbug package. If you don't have a working mailer daemon (MTA) on your machine, be sure to tell it that when you first run reportbug. If you've got a set of patches to send named 000?-* (say from git format-patch), then:

reportbug --source sourcepackagename --attach '000*'

and then answer the questions about severity (should be wishlist) and indicate that there is a patch. Alternatively, if you like long command lines you can do it all in one step (tab completion also works for these options):

reportbug --source sourcepackagename --attach '000*' --tag patch --severity wishlist

A couple of other useful bits of information:

Other mailing lists

Online resources