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

Re: New python policy



Steve Langasek writes:
> On Fri, Jun 02, 2006 at 11:50:53AM -0500, Joe Wreschnig wrote:
> > On Fri, 2006-06-02 at 12:52 +0200, Raphael Hertzog wrote:
> > > * the dependencies (hopefully created automatically by dh_python) will
> > >   indicate the right interval automatically:
> > >   right now for example it would be "python (>=2.3), python (<< 2.5)"
> > >   for a package saying "XC-Python-Version: all"
> 
> > What's the point of such a tight upper dependency? The whole idea was to
> > reduce the work for transitions, this still requires a rebuild when we
> > upgrade to Python 2.5 (or in fact, whenever the supported versions of
> > Python change).
> 
> > Such information is necessary for extensions, but irrelevant for
> > programs or other modules.
> 
> Indeed, the intent was that this strict upper bound would apply to
> extensions, not to modules.  Not sure if that intent got lost somewhere
> along the way.

IIRC We did conclude that we need the Provides: pythonX.Y-foo for
modules as well and have to regenerate this information if we change
the set of supported python versions.



Reply to: