Revision 1 as of 2011-03-14 06:12:26

Clear message

Attendees

Agenda

Day 1

Pending

Day 1

Status of python3 third-party modules 1

Brief discussion on this topic. Deferred further discussion for two reasons:

  1. bento maintainer and distutils2 maintainers present for tonight. Talk to them about issues which concern them.
  2. Allison Randal not present tonight

Have to engage upstreams

How do we market to upstream that we (distro maintainers) want to help create patches for python3?

gtk/gnome

setuptools

Actions

Multiple versions 1

Goals

Any solution has two parts -- what do we do in python and what do we do in the distros.

A current solution

Caveats

A new ENVVAR specifying config files

Why not just use PYTHONPATH?

The location of the package will need to depend on both the python package name and its version. For instance: /usr/lib/python2.7/site-packages/foo-1.0/foo This location specifies and exact version. PYTHONPATH would require us to specify that exact version as well: PYTHONPATH=/usr/lib/python2.7/site-packages/foo-1.0/foo. This will break the moment we upgrade to a different version of foo even if it's API compatible. Using a config file means that we get a range of versions.

Questions

What, if anything, should core python know about this directory structure? Should the python docs suggest a standard location?

Actions

Duplicate named modules

Problem, sometimes there's more than one python module that shares the same name. then we have to get someone to rename modules.

Actions

Numpy

Quick questions about packaging best practices and the FHS.

Namespace packages

Some questions about how namespace packages will affect python

Unable to edit the page? See the FrontPage for instructions.