Brett Cannon wrote:
> Could, but the code will go away some day and not everyone will read the
> docs to realize that they might want to upgrade their code if they care
> to use the shiniest thing in the standard library.
I agree with Brett here - PendingDeprecationWarning for "there's a
better op
On Sun, Feb 21, 2010 at 14:46, Eric Smith wrote:
> Brett Cannon wrote:
>
>> Yes, DeprecationWarning is now silent under Python 2.7 and 3.1 so a
>> DeprecationWarning would only pop up if developers exposed
>> DeprecationWarning. But if the module is not about to be removed in 3.x then
>> I think
Brett Cannon wrote:
Yes, DeprecationWarning is now silent under Python 2.7 and 3.1 so a
DeprecationWarning would only pop up if developers exposed
DeprecationWarning. But if the module is not about to be removed in 3.x
then I think regardless of the silence of both warnings it should stay
Pend
On Sun, Feb 21, 2010 at 13:31, Guido van Rossum wrote:
> On Sun, Feb 21, 2010 at 1:26 PM, Steven Bethard
> wrote:
> > On Sun, Feb 21, 2010 at 5:45 AM, Guido van Rossum
> wrote:
> >> Maybe the best thing is to make optparse *silently* deprecated, with a
> >> big hint at the top of its documentat
On Sun, Feb 21, 2010 at 10:31 AM, Guido van Rossum wrote:
> On Sun, Feb 21, 2010 at 1:26 PM, Steven Bethard
> wrote:
>> So basically do what the PEP does now, except don't remove optparse in
>> Python 3.5? For reference, the current proposal is:
>>
>> * Python 2.7+ and 3.2+ -- The following not
On Sun, Feb 21, 2010 at 1:26 PM, Steven Bethard
wrote:
> On Sun, Feb 21, 2010 at 5:45 AM, Guido van Rossum wrote:
>> Maybe the best thing is to make optparse *silently* deprecated, with a
>> big hint at the top of its documentation telling new users to use
>> argparse instead, but otherwise leavi
Thanks all for the updates. Sorry I can't make it to PyCon this year!
On Sun, Feb 21, 2010 at 1:30 AM, Eric Smith wrote:
> There was also a quick discussion on maybe implementing optparse using
> argparse, then getting rid of the existing optparse.
I think the PEP pretty much already covers why
2010/2/21 :
>
> Guido> Maybe the best thing is to make optparse *silently* deprecated,
> Guido> with a big hint at the top of its documentation telling new users
> Guido> to use argparse instead, but otherwise leaving it in indefinitely
> Guido> for the benefit of the many existing use
Guido> Maybe the best thing is to make optparse *silently* deprecated,
Guido> with a big hint at the top of its documentation telling new users
Guido> to use argparse instead, but otherwise leaving it in indefinitely
Guido> for the benefit of the many existing users.
Would a 2to3
On 21/02/2010 08:45, Guido van Rossum wrote:
On Sun, Feb 21, 2010 at 4:30 AM, Eric Smith wrote:
Steven Bethard wrote:
On Fri, Feb 19, 2010 at 7:50 AM, Brett Cannon wrote:
My notes from the session I led:
+ argparse
- Same issues brought up.
For those of us n
On Sun, Feb 21, 2010 at 4:30 AM, Eric Smith wrote:
> Steven Bethard wrote:
>>
>> On Fri, Feb 19, 2010 at 7:50 AM, Brett Cannon wrote:
>>>
>>> My notes from the session I led:
>>>
>>> + argparse
>>>
>>> - Same issues brought up.
>>
>> For those of us not at PyCon, what were the issues?
>
> I thi
Steven Bethard wrote:
On Fri, Feb 19, 2010 at 7:50 AM, Brett Cannon wrote:
My notes from the session I led:
+ argparse
- Same issues brought up.
For those of us not at PyCon, what were the issues?
I think they were all related to deprecation of optparse, not anything
to do with argpar
On Fri, Feb 19, 2010 at 7:50 AM, Brett Cannon wrote:
> My notes from the session I led:
>
> + argparse
>
> - Same issues brought up.
For those of us not at PyCon, what were the issues?
Steve
--
Where did you get that preposterous hypothesis?
Did Steve tell you that?
--- The Hiphopopo
My notes from the session I led:
+ argparse
- Same issues brought up.
+ Hg transition
- Just updated everyone; Dirkjan said everything I did in his email update.
+ Stdlib breakout
- Mentioned; nothing planned beyond a PEP at some point.
+ Extension module policy
- If you wri
14 matches
Mail list logo
