[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposed update to the python policy



On Wed, Mar 21, 2007 at 10:59:40PM +0100, Piotr Ożarowski wrote:
> [Steve Langasek, 21.03.2007]
> > 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?

> I think depending on python-dev for current only modules/apps and
> python-all-dev for the rest should be enough (if both systems will
> recognize it correctly, I mean also: "python-dev(>=2.5)|python2.5-dev" )

No, this has nothing to do with the question of being able to get the
version number of, and build binary extensions for, the current version of
python.

-- 
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: