Re: Proposed update to the python policy
On Wed, Mar 21, 2007 at 10:47:37PM +0100, Josselin Mouette wrote:
> Le mercredi 21 mars 2007 à 14:44 -0700, Steve Langasek a écrit :
> > On Wed, Mar 21, 2007 at 08:22:32PM +0100, Josselin Mouette wrote:
> > > I think it's time to update the python policy with the progress that has
> > > been made in how we build python packages. The proposed diff is
> > > attached. In summary it includes:
> > > * the deprecation of the "current" keyword;
> > So with current deprecated, what is the solution for a package which wants
> > to build a single binary extension for the current python version in a
> > package named python-foo, with no support for other versions of python
> > returned by pyversions -s?
> If this is a public extension, this goes completely against the spirit
> of the policy and should not be allowed. It just means more packages
> having to migrate simultaneously with python-defaults.
It's not against the spirit of what was discussed in Mexico, it's just
against the spirit of what you personally think.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to: