On Tue, Dec 15, 2009 at 12:37 AM, Steven Bethard
wrote:
>
> If you're only concerned about 2.X, then yes, optparse will *never* be
> removed from 2.X. There will be a deprecation note in the 2.X
> documentation but deprecation warnings will only be issued when the -3
> flag is specified. Please se
On Sun, Dec 27, 2009 at 9:51 AM, anatoly techtonik wrote:
> On Tue, Dec 15, 2009 at 12:37 AM, Steven Bethard
> wrote:
>>
>> If you're only concerned about 2.X, then yes, optparse will *never* be
>> removed from 2.X. There will be a deprecation note in the 2.X
>> documentation but deprecation warn
On Fri, Dec 25, 2009 at 8:33 AM, Nick Coghlan wrote:
> Martin v. Löwis wrote:
>>> I'll remove it and push it in Distutils documentation, then might just
>>> provide a link in the PEP References.
>>
>> That sounds fine to me.
>
> That would address my questions as well - someone looking for a guide
> On Fri, Dec 25, 2009 at 8:33 AM, Nick Coghlan wrote:
>> Martin v. Löwis wrote:
> FYI we have introduced a range operator, so one may define a range of
> versions.
> This is useful for instance to write:
>
> Requires-Python: ~=2.5
>
> Which means: requires any version of Python 2.5.x. This oper
On Mon, Dec 28, 2009 at 1:15 AM, wrote:
>> On Fri, Dec 25, 2009 at 8:33 AM, Nick Coghlan wrote:
>>> Martin v. Löwis wrote:
>> FYI we have introduced a range operator, so one may define a range of
>> versions.
>> This is useful for instance to write:
>>
>> Requires-Python: ~=2.5
>>
>> Which mea
On 12/27/2009 4:15 PM, david.l...@preisshare.net wrote:
On Fri, Dec 25, 2009 at 8:33 AM, Nick Coghlan wrote:
>> Martin v. Löwis wrote:
> FYI we have introduced a range operator, so one may define a range of
> versions.
> This is useful for instance to write:
>
> Requires-Python: ~=2.5
Tarek Ziadé gmail.com> writes:
>
> This was ambiguous because it was unclear, as MvL stated, if "2.5"
> was just "2.5.0" or included
> versions like "2.5.1" or "2.5.2".
How about having "2.5" match all 2.5.x versions, and "2.5.0" match only 2.5
itself? (ditto for "2.5.N" matching only 2.5.N for
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
wrote:
[..]
>
> Tarek,
>
> I am a bit confused at the current proposal combined with the newly
> introduced range operator.
>
> Would "Requires-Python: <=2.5" include 2.5.4 or not?
<=2.5 means any version that is inferior or equal to 2.5.0 so 2.
> No application developer will quickly figure out what a tilde means. Maybe
> it means 'roughly', but it requires too much thought and is ambiguous. 2.5
> is not roughly 2.5.2. It is the same exactly.
>
> Before we had : Requires-Python: 2.5, 2.6
>
> That made much more sense. It was simple and
On Mon, Dec 28, 2009 at 1:48 AM, Antoine Pitrou wrote:
> Tarek Ziadé gmail.com> writes:
>>
>> This was ambiguous because it was unclear, as MvL stated, if "2.5"
>> was just "2.5.0" or included
>> versions like "2.5.1" or "2.5.2".
>
> How about having "2.5" match all 2.5.x versions, and "2.5.0" m
Tarek Ziadé writes:
> FYI we have introduced a range operator, so one may define a range of
> versions. This is useful for instance to write:
>
> Requires-Python: ~=2.5
>
> Which means: requires any version of Python 2.5.x.
-1 on that syntax. It's an extra operator, with a non-obvious meaning;
Tarek Ziadé wrote:
> On Mon, Dec 28, 2009 at 1:48 AM, Antoine Pitrou wrote:
>> Tarek Ziadé gmail.com> writes:
>>> This was ambiguous because it was unclear, as MvL stated, if "2.5"
>>> was just "2.5.0" or included
>>> versions like "2.5.1" or "2.5.2".
>> How about having "2.5" match all 2.5.x ve
Tarek Ziadé writes:
> On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
> wrote:
> > Also, "Requires-Python: 3" would include all 3.X versions, correct?
>
> Correct, because, "Requires-Python: 3" is equivalent to
> "Requires-Python: ~= 3" which is equivalent to "Requires-Python:
> 3.x.x"
This
Tarek Ziadé wrote:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
wrote:
[..]
Tarek,
I am a bit confused at the current proposal combined with the newly
introduced range operator.
Would "Requires-Python: <=2.5" include 2.5.4 or not?
<=2.5 means any version that is inferior or equal to
2009-12-28 02:17:22 Ben Finney napisał(a):
> Tarek Ziadé writes:
>
> > On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
> > wrote:
> > > Also, "Requires-Python: 3" would include all 3.X versions, correct?
> >
> > Correct, because, "Requires-Python: 3" is equivalent to
> > "Requires-Python: ~=
Ben Finney wrote:
Tarek Ziadé writes:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
wrote:
Also, "Requires-Python: 3" would include all 3.X versions, correct?
Correct, because, "Requires-Python: 3" is equivalent to
"Requires-Python: ~= 3" which is equivalent to "Requires-Python:
3.x.x
On Sun, Dec 27, 2009 at 8:28 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> 'Requires-Python: 3*' (or '3.*') would be better than 'Requires-Python: >=3,
> <4'.
Maybe.
MRAB wrote:
> Requires-Python: 3 ~ 4
Ugh. -1
-Fred
--
Fred L. Drake, Jr.
"Chaos is the score upon which reality is
On Dec 27, 2009, at 8:02 PM, Tarek Ziadé wrote:
> On Mon, Dec 28, 2009 at 1:48 AM, Antoine Pitrou wrote:
>> Tarek Ziadé gmail.com> writes:
>>>
>>> This was ambiguous because it was unclear, as MvL stated, if "2.5"
>>> was just "2.5.0" or included
>>> versions like "2.5.1" or "2.5.2".
>>
>> H
On 12/27/2009 5:21 PM, MRAB wrote:
Tarek Ziadé wrote:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
wrote:
[..]
Tarek,
I am a bit confused at the current proposal combined with the newly
introduced range operator.
Would "Requires-Python: <=2.5" include 2.5.4 or not?
<=2.5 means any v
Martin v. Löwis wrote:
No application developer will quickly figure out what a tilde means. Maybe
it means 'roughly', but it requires too much thought and is ambiguous. 2.5
is not roughly 2.5.2. It is the same exactly.
Before we had : Requires-Python: 2.5, 2.6
That made much more sense. It was
Arfrever Frehtes Taifersar Arahesis wrote:
2009-12-28 02:17:22 Ben Finney napisał(a):
Tarek Ziadé writes:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
wrote:
Also, "Requires-Python: 3" would include all 3.X versions, correct?
Correct, because, "Requires-Python: 3" is equivalent to
"
Ben Finney writes:
> Instead, the default should be `=='. That is, `Requires-Python: 3'
> should be equivalent to `Requires-Python: ==3'; and only "3" or "3.0" or
> "3.0.0" etc. will match. I maintain that is what most people will expect
> on seeing that syntax.
I really don't think your asse
>> No application developer will quickly figure out what a tilde means.
>> Maybe
>> it means 'roughly', but it requires too much thought and is ambiguous.
>> 2.5
>> is not roughly 2.5.2. It is the same exactly.
>>
>> Before we had : Requires-Python: 2.5, 2.6
>>
>> That made much more sense. It was
> Instead, the default should be â==â. That is, âRequires-Python: 3â
> should be equivalent to âRequires-Python: ==3â; and only â3â or
> â3.0â or
> â3.0.0â etc. will match. I maintain that is what most people will
> expect
> on seeing that syntax.
>
> If a less strict range
On Mon, Dec 21, 2009 at 7:02 AM, Mark Dickinson wrote:
> In Python 2.7, PyArg_ParseTuple and friends currently accept a float
> argument where an integer is expected, but produce a
> DeprecationWarning in this case. This can be seen in various places
> in Python proper:
>
itertools.combinati
On 12/27/2009 7:48 PM, Antoine Pitrou wrote:
Tarek Ziadé gmail.com> writes:
This was ambiguous because it was unclear, as MvL stated, if "2.5"
was just "2.5.0" or included
versions like "2.5.1" or "2.5.2".
How about having "2.5" match all 2.5.x versions, and "2.5.0" match only 2.5
itself?
>> Tarek Ziadé gmail.com> writes:
> An implicit range operator is simpler indeed, and achieves the same goal.
>
> Meaning that "<=2.5" for example, will be translated to "<=2.5.x" as well.
With respect, it's not a very common use case for a developer to
say that package needs a python interpretor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry Reedy wrote:
> On 12/27/2009 7:48 PM, Antoine Pitrou wrote:
>> Tarek Ziadé gmail.com> writes:
>>> This was ambiguous because it was unclear, as MvL stated, if "2.5"
>>> was just "2.5.0" or included
>>> versions like "2.5.1" or "2.5.2".
>> How
david.l...@preisshare.net writes:
> >> Before we had : Requires-Python: 2.5, 2.6
> >>
> >> That made much more sense. It was simple and unambiguous, and is
> >> relevant to typical packaging scenarios.
> >
> > Unfortunately, it is fairly ambiguous, and makes no sense. It means
> > "requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tarek Ziadé wrote:
> On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
> wrote:
> [..]
>> Tarek,
>>
>> I am a bit confused at the current proposal combined with the newly
>> introduced range operator.
>>
>> Would "Requires-Python: <=2.5" include 2.5
On Mon, Dec 28, 2009 at 05:37, Terry Reedy wrote:
> If the first x.y release were called x.y.0, (does not sys.version include
> 0?) then x.y would unambiguously mean the series.
Yeah, well, although sys.version includes the zero, nothing else does.
The first releases are called 2.5, which is ambi
david.l...@preisshare.net writes:
> With respect, it's not a very common use case for a developer to
> say that package needs a python interpretor 'older' than 2.5.
Of course it is. I don't claim it is the majority of cases out there,
but stable versions of many of the packages I use will spec
> And in fact this case is often more the important one. Packages that
> depend on having a *recent* version of python will often crash
> quickly, before doing permanent damage, when an undefined syntax,
> function, or method is invoked, while packages that depend on a quirk
> in behavior of an o
> david.l...@preisshare.net writes:
>
> > With respect, it's not a very common use case for a developer to
> > say that package needs a python interpretor 'older' than 2.5.
>
> Of course it is. I don't claim it is the majority of cases out there,
> but stable versions of many of the packages I u
34 matches
Mail list logo
