Thanks for everyone's comments. Sent:
http://lists.debian.org/debian-release/2010/06/msg00211.html
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100625
Il giorno Wed, 23 Jun 2010 13:15:46 -0400
Scott Kitterman ha scritto:
> I have consulted with Luca Falavigna (DktrKranz) and Jakub Wilk (jwilk), who
> did most of the analysis for the last two Python transitions (Adding 2.6 to
> supported versions and the current transition to 2.6 as default) a
"Josselin Mouette" wrote:
>Le mercredi 23 juin 2010 à 21:17 -0400, Scott Kitterman a écrit :
>> >5. End this madness and use the version in build-dependencies instead of
>> >asking maintainers to specify it twice - which they usually do wrong.
>> >
>> With this approach then with the current py
On Thu, Jun 24, 2010 at 12:35 PM, Piotr Ożarowski wrote:
>> * A module that works perfectly with every Python >= 2.5, but its
>> documentation generation system required Python 2.6. Build-dep on python
>> (>= 2.6) is needed, which doesn't mean that modules shouldn't be
>> byte-compiled for 2.5.
>
[Jakub Wilk, 2010-06-24]
> * Piotr Ożarowski , 2010-06-24, 09:27:
>> it gets a little bit messy when minimum required Python version is
>> greater than the default one, but it should work, yes (IIRC last year
>> someone gave me example where it wouldn't work, but I don't remember it
>> now, hopeful
* Piotr Ożarowski , 2010-06-24, 09:27:
5. End this madness and use the version in build-dependencies
instead of asking maintainers to specify it twice - which they
usually do wrong.
With this approach then with the current python-defaults in Sid, how
would one specify works with 2.5 and 2.6, bu
[Piotr Ożarowski, 2010-06-24]
> [Josselin Mouette, 2010-06-24]
> example for default=3.1 minimum=3.2 maximum=3.5:
> python-all | python-all (>= 3.2), python-all (<< 3.5), python-all (>=
> 3.1.2-2)
> or even
> python-all (>= 3.1.2-2) | python-all (>= 3.2), python-all (<< 3.5)
err, python3-all of
[Josselin Mouette, 2010-06-24]
> Le mercredi 23 juin 2010 à 21:17 -0400, Scott Kitterman a écrit :
> > >5. End this madness and use the version in build-dependencies instead of
> > >asking maintainers to specify it twice - which they usually do wrong.
> > >
> > With this approach then with the curr
Le mercredi 23 juin 2010 à 21:17 -0400, Scott Kitterman a écrit :
> >5. End this madness and use the version in build-dependencies instead of
> >asking maintainers to specify it twice - which they usually do wrong.
> >
> With this approach then with the current python-defaults in Sid, how would
>
On Thu, Jun 24, 2010 at 12:44:36AM -0400, Scott Kitterman wrote:
> On Wednesday, June 23, 2010 11:08:47 pm Paul Wise wrote:
> > On Thu, Jun 24, 2010 at 10:42 AM, Scott Kitterman
> wrote:
> > > The email is meant to go to the release team to address what I understand
> > > to be release team speci
On Wednesday, June 23, 2010 11:08:47 pm Paul Wise wrote:
> On Thu, Jun 24, 2010 at 10:42 AM, Scott Kitterman
wrote:
> > The email is meant to go to the release team to address what I understand
> > to be release team specific requirement. I think that the broader
> > question needs to be discuss
On Thu, Jun 24, 2010 at 10:42 AM, Scott Kitterman wrote:
> The email is meant to go to the release team to address what I understand to
> be release team specific requirement. I think that the broader question needs
> to be discussed in a broader audience.
I think it is relevant there as well,
On Wednesday, June 23, 2010 10:01:03 pm Paul Wise wrote:
> On Thu, Jun 24, 2010 at 1:15 AM, Scott Kitterman
wrote:
> > In Debian Python we are currently discussing how best to specify version
> > information for Python 3. There is a strong (but not unanimous) view
> > among the participants in d
On Thu, Jun 24, 2010 at 1:15 AM, Scott Kitterman wrote:
> In Debian Python we are currently discussing how best to specify version
> information for Python 3. There is a strong (but not unanimous) view among
> the participants in debian-pyt...@l.d.o and #debian-python that Python(2) and
> Python
"Josselin Mouette" wrote:
>Le mercredi 23 juin 2010 à 13:15 -0400, Scott Kitterman a écrit :
>> 1. Use XS/B-P-V for Python and Python3 versions
>> 2. Create a new set of fields, XS/B-Python3-Version.
>> 3. Create a new field, X-Python-Version: for Python3 versions.
>> 4. Create a new field,
Le mercredi 23 juin 2010 à 13:15 -0400, Scott Kitterman a écrit :
> 1. Use XS/B-P-V for Python and Python3 versions
> 2. Create a new set of fields, XS/B-Python3-Version.
> 3. Create a new field, X-Python-Version: for Python3 versions.
> 4. Create a new field, X-Python3-Version: for Python3 ver
"Piotr Ożarowski" wrote:
>[Scott Kitterman, 2010-06-23]
>> 3. Create a new field, X-Python-Version: for Python3 versions. This avoids
>> concerns about control file bloat, but may be a bit confusing in combination
>> with the existing XS/B-P-V.
>
>+ "Please note the lack of XB-Python-Versio
[Scott Kitterman, 2010-06-23]
> 3. Create a new field, X-Python-Version: for Python3 versions. This avoids
> concerns about control file bloat, but may be a bit confusing in combination
> with the existing XS/B-P-V.
+ "Please note the lack of XB-Python-Version, i.e. X-Python-Version
will be us
18 matches
Mail list logo
