Re: collecting Python 3 status information
On 02/20/2011 11:16 PM, Robert Collins wrote:
I think you need an upstream status field, for instance for
python-testtools which is single-source python 3.2+ compatible, but
may not be packaged thusly.
Ah, thanks, yes the field needs a clearer name. I've changed "Notes" to
"Upstream Python 3 Plans". For the distros, we really only need a short
status tag ("packaged", "not packaged", "waiting for upstream", "won't
package", etc), but for the upstreams we'll need any details we can
gather about whether, when, and how they plan to migrate.
Allison
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: collecting Python 3 status information
I think you need an upstream status field, for instance for python-testtools which is single-source python 3.2+ compatible, but may not be packaged thusly. -Rob -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
collecting Python 3 status information
Matthias, Barry, and I are working on collecting information about Python packages and when/whether they're planning to migrate to Python 3. Some of that information can only be collected manually, so we're hoping to get some help. I've generated a wiki page of source packages in main that depend on Python, as an open frame where anyone can contribute: https://wiki.ubuntu.com/AllisonRandal/Python3Status The highlighted rows are a higher priority because they're needed for the CD (calculated from the seeds). The homepage is listed when the package specified one, as a clue in the search. The page also lists dependency details, to help in determining how much work is involved in the migration: a package that directly depends on Python likely has more Python code involved than a package that only indirectly depends on a tool that depends on a library that depends on Python. The information collected here won't just stay as a static wiki page, I'll suck it into a database and use it in various reports and progress checks. Ultimately, we'd like to make this information available to python.org to help the overall Python 3 migration effort. Thanks, Allison -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
