I've implemented this and put the patch in Issue8451:
http://bugs.python.org/issue8451
I'm happy with how it is now, including documentation, but would like some
review.
Thanks,
Sean
--
Sean Reifschneider, Member of Technical Staff
tummy.com, ltd. - Linux Consulting since 1995: Ask me about
On Sun, Apr 18, 2010 at 7:02 PM, Ian Bicking wrote:
> Somewhat relatedly, what is the plan for past and future argparse releases?
I currently don't have any plans to make releases outside of the main
Python releases. Perhaps if there's great demand for it, I'll
reconsider, but as it is, I haven't
On Sun, Apr 18, 2010 at 6:40 PM, Nick Coghlan wrote:
> Note there are two changes I believe should be made to the argparse
> documentation for 2.7 though:
> - the '--version' example should either not use a shorthand, or should
> use the conventional '-V'
> - this issue needs to be mentioned in th
On Sun, Apr 18, 2010 at 4:35 PM, Nick Coghlan wrote:
> Steven Bethard wrote:
>> On Sun, Apr 18, 2010 at 3:57 PM, Nick Coghlan wrote:
>>> Steven Bethard wrote:
By the way, we could simplify the typical add_argument usage by adding
"show program's version number and exit" as the default h
> - many optparse programs use the version argument
> - many other programmers find this feature very convenient
> - dropping or deprecating this is a totally unnecessary change
> (I have not read a single real reason /why/ this should be done).
You actually brought up a good reason yourself:
I
On 04/18/2010 06:35 PM, Nick Coghlan wrote:
Steven Bethard wrote:
On Sun, Apr 18, 2010 at 3:57 PM, Nick Coghlan wrote:
Steven Bethard wrote:
By the way, we could simplify the typical add_argument usage by adding
"show program's version number and exit" as the default help for the
'version'
On 04/18/2010 05:57 PM, Nick Coghlan wrote:
Steven Bethard wrote:
By the way, we could simplify the typical add_argument usage by adding
"show program's version number and exit" as the default help for the
'version' action. Then you should just write:
parser.add_argument('--version', act
Cameron Simpson wrote:
> On 18Apr2010 22:52, Antoine Pitrou wrote:
> | Steven Bethard gmail.com> writes:
> | > I
> | > need to a see a consensus from a variety of developers that
> | > "--version" is the right answer, and not "-V/--version", etc.
> |
> | Both are ok for me. "-v" as a shortcut fo
Tobias Herp writes:
> Steven Bethard schrieb:
> > On Sun, Apr 18, 2010 at 3:52 PM, Antoine Pitrou wrote:
> >> Steven Bethard gmail.com> writes:
> >>> Note that even though I agree with you that "-v/--version" is
> >>> probably not the best choice, in the poll[2] 11% of people still
> >>> wanted
On Apr 18, 2010, at 07:30 PM, Eric Smith wrote:
>Steven Bethard wrote:
>> By the way, we could simplify the typical add_argument usage by adding
>> "show program's version number and exit" as the default help for the
>> 'version' action. Then you should just write:
>>
>> parser.add_argument('
On Sun, Apr 18, 2010 at 6:24 PM, Steven Bethard wrote:
> On Sun, Apr 18, 2010 at 3:52 PM, Antoine Pitrou
> wrote:
> > Steven Bethard gmail.com> writes:
> >> Note
> >> that even though I agree with you that "-v/--version" is probably not
> >> the best choice, in the poll[2] 11% of people still wa
Tobias Herp wrote:
> Steven Bethard schrieb:
>> On Sun, Apr 18, 2010 at 2:35 PM, Tobias Herp wrote:
>>> Steven Bethard schrieb:
On Sun, Apr 18, 2010 at 3:31 AM, Tobias Herp wrote:
> *Argparse should simply do this like optparse does already.*
> I.e., use '--version', '--help' and '-h
On 18Apr2010 22:52, Antoine Pitrou wrote:
| Steven Bethard gmail.com> writes:
| > I
| > need to a see a consensus from a variety of developers that
| > "--version" is the right answer, and not "-V/--version", etc.
|
| Both are ok for me. "-v" as a shortcut for "--version" looks wrong, though.
|
Tobias Herp wrote:
> Be careful. There have been other personal opinions, and there are very
> many *X programs which form a standard which should be followed, and
> this is a /very strong/ argument, IMO.
If the "version=" argument were to only provide "--version", how would
you conveniently add
Steven Bethard schrieb:
> On Sun, Apr 18, 2010 at 2:35 PM, Tobias Herp wrote:
>> Steven Bethard schrieb:
>>> On Sun, Apr 18, 2010 at 3:31 AM, Tobias Herp wrote:
*Argparse should simply do this like optparse does already.*
I.e., use '--version', '--help' and '-h' by default, but not '-v'
Steven Bethard schrieb:
> On Sun, Apr 18, 2010 at 3:52 PM, Antoine Pitrou wrote:
>> Steven Bethard gmail.com> writes:
>>> Note
>>> that even though I agree with you that "-v/--version" is probably not
>>> the best choice, in the poll[2] 11% of people still wanted this.
>>
>> This strikes me as a
Eric Smith schrieb:
> Steven Bethard wrote:
>> By the way, we could simplify the typical add_argument usage by adding
>> "show program's version number and exit" as the default help for the
>> 'version' action. Then you should just write:
>>
>> parser.add_argument('--version', action='version',
Steven Bethard wrote:
> On Sun, Apr 18, 2010 at 3:57 PM, Nick Coghlan wrote:
>> Steven Bethard wrote:
>>> By the way, we could simplify the typical add_argument usage by adding
>>> "show program's version number and exit" as the default help for the
>>> 'version' action. Then you should just write
Steven Bethard wrote:
By the way, we could simplify the typical add_argument usage by adding
"show program's version number and exit" as the default help for the
'version' action. Then you should just write:
parser.add_argument('--version', action='version', version='')
I like this the bes
On Sun, Apr 18, 2010 at 3:52 PM, Antoine Pitrou wrote:
> Steven Bethard gmail.com> writes:
>> Note
>> that even though I agree with you that "-v/--version" is probably not
>> the best choice, in the poll[2] 11% of people still wanted this.
>
> This strikes me as a small minority.
Agreed, but it'
On Sun, Apr 18, 2010 at 3:57 PM, Nick Coghlan wrote:
> Steven Bethard wrote:
>> By the way, we could simplify the typical add_argument usage by adding
>> "show program's version number and exit" as the default help for the
>> 'version' action. Then you should just write:
>>
>> parser.add_argum
Victor Stinner wrote:
> Le samedi 17 avril 2010 20:41:10, Victor Stinner a écrit :
>> Ezio and Florent are developing a tool called bbreport to collect buildbot
>> results and generate short reports to the command line. (...)
>
> I realized that most issues come from Windows and Mac. Can't we just
On 19/04/2010 00:52, Antoine Pitrou wrote:
Steven Bethard gmail.com> writes:
I
need to a see a consensus from a variety of developers that
"--version" is the right answer, and not "-V/--version", etc.
Both are ok for me. "-v" as a shortcut for "--version" looks wrong, though. "-v"
i
Steven Bethard wrote:
> By the way, we could simplify the typical add_argument usage by adding
> "show program's version number and exit" as the default help for the
> 'version' action. Then you should just write:
>
> parser.add_argument('--version', action='version', version=' version>')
Wit
Steven Bethard gmail.com> writes:
>
> I
> need to a see a consensus from a variety of developers that
> "--version" is the right answer, and not "-V/--version", etc.
Both are ok for me. "-v" as a shortcut for "--version" looks wrong, though. "-v"
is almost always used for verbosity these days.
On Sun, Apr 18, 2010 at 2:35 PM, Tobias Herp wrote:
> Steven Bethard schrieb:
>> On Sun, Apr 18, 2010 at 3:31 AM, Tobias Herp wrote:
>>> *Argparse should simply do this like optparse does already.*
>>> I.e., use '--version', '--help' and '-h' by default, but not '-v'.
>> [snip]
>>> The deprecatio
Le samedi 17 avril 2010 20:41:10, Victor Stinner a écrit :
> Ezio and Florent are developing a tool called bbreport to collect buildbot
> results and generate short reports to the command line. (...)
I realized that most issues come from Windows and Mac. Can't we just turn off
these buildbots?
-
Steven Bethard schrieb:
> On Sun, Apr 18, 2010 at 4:03 AM, Nick Coghlan wrote:
>> To deal with this in a backwards compatible way while remaining on the
>> path to more conventional behaviour, I suggest the following:
>>
>> 1. For Python 2.7, deprecate *just* the "-v" default behaviour for the
>>
Steven Bethard schrieb:
> On Sun, Apr 18, 2010 at 3:31 AM, Tobias Herp wrote:
>> To put it short:
>> *Argparse should simply do this like optparse does already.*
>> I.e., use '--version', '--help' and '-h' by default, but not '-v'.
> [snip]
>> What happened was the following:
>> Completely unneces
Ronald Oussoren writes:
> On 18 Apr, 2010, at 17:17, Martin v. Löwis wrote:
>
>> Ronald Oussoren wrote:
>>>
>>> That *is* trivial: use Mac/BuildScript/build-installer.py on OSX 10.5.
>>
>> Hmm. When I tried it (on some 2.5 release), it took me two days until it
>> produced something.
>
> It sho
"Martin v. Löwis" writes:
>> I do currently have a DMG built for 2.7 Beta 1, if it would be useful.
>
> As I said before: if you would plan to do this on a regular basis, for
> all upcoming releases, that would certainly be a good thing.
No argument - just figured I'd offer to get past the near
On Sun, Apr 18, 2010 at 4:03 AM, Nick Coghlan wrote:
> To deal with this in a backwards compatible way while remaining on the
> path to more conventional behaviour, I suggest the following:
>
> 1. For Python 2.7, deprecate *just* the "-v" default behaviour for the
> version. This means "--version"
On Sun, Apr 18, 2010 at 3:31 AM, Tobias Herp wrote:
> To put it short:
> *Argparse should simply do this like optparse does already.*
> I.e., use '--version', '--help' and '-h' by default, but not '-v'.
[snip]
> What happened was the following:
> Completely unnecessarily, the 'version' constructor
> Does it really need trunk? I've been running it under 2.6 without
> problems, but I probably haven't explored all the options fully.
>
Now it works on 2.6 (or 2.5+pysqlite).
Regards,
--
Florent
___
Python-Dev mailing list
Python-Dev@python.org
http
On Sun, Apr 18, 2010 at 10:16, wrote:
> On 02:56 pm, techto...@gmail.com wrote:
>
>> Twisted folks will surely appreciate any help and may be able to
>> contribute back.
>> http://twistedmatrix.com/trac/wiki/Windows
>>
>
> Extra Windows and VS licenses would certainly be helpful for Twisted
> dev
On 18 Apr, 2010, at 17:20, Martin v. Löwis wrote:
>> We can certainly start by just trying to automate the execution of
>> build-installer, something I suspect can be completely controlled from
>> the master side, and then uploading the resulting dmg file. I'd be
>> happy to help coordinate any
> We can certainly start by just trying to automate the execution of
> build-installer, something I suspect can be completely controlled from
> the master side, and then uploading the resulting dmg file. I'd be
> happy to help coordinate any experiments offline if you're interested.
Sure!
> I do
On 18 Apr, 2010, at 17:17, Martin v. Löwis wrote:
> Ronald Oussoren wrote:
>> On 15 Apr, 2010, at 6:36, Martin v. Löwis wrote:
>>
>>> Greg Ewing wrote:
Michael Foord wrote:
> Building Python requires, I believe, the XCode development tools to be
> installed. Even then, building a fu
Ronald Oussoren wrote:
> On 15 Apr, 2010, at 6:36, Martin v. Löwis wrote:
>
>> Greg Ewing wrote:
>>> Michael Foord wrote:
Building Python requires, I believe, the XCode development tools to be
installed. Even then, building a full version of Python - with *all*
the C extensions that
On 02:56 pm, techto...@gmail.com wrote:
Twisted folks will surely appreciate any help and may be able to
contribute back.
http://twistedmatrix.com/trac/wiki/Windows
Extra Windows and VS licenses would certainly be helpful for Twisted
development, and might lead indirectly to CPython/Windows im
> what's the status of backporting PEP 3102 ?
It looks like it won't happen.
> It was supposed to go into
> 2.6 and it seems it won't be in 2.7 either.
Correct - and therefore, it won't be backported at all.
> There is an updated patch
> in the tracker [1] that applies cleanly on the latest t
Twisted folks will surely appreciate any help and may be able to
contribute back.
http://twistedmatrix.com/trac/wiki/Windows
--
anatoly t.
On Fri, Apr 16, 2010 at 4:01 PM, Brian Curtin wrote:
> Hi python-dev,
>
> The recent threads on builds/installers for Mac and Windows reminded me of
> Ste
On 15 Apr, 2010, at 6:36, Martin v. Löwis wrote:
> Greg Ewing wrote:
>> Michael Foord wrote:
>>> Building Python requires, I believe, the XCode development tools to be
>>> installed. Even then, building a full version of Python - with *all*
>>> the C extensions that are part of a Python release -
On 15 Apr, 2010, at 0:12, Zvezdan Petkovic wrote:
> On Apr 14, 2010, at 4:40 PM, Martin v. Löwis wrote:
>
>>> I think you just need to supply to configure
>>>
>>> MACOSX_DEPLOYMENT_TARGET=10.4
>>>
>>> and have the appropriate SDK installed with Xcode.
>>
>> Wouldn't that break 10.3 compatibil
On 14 Apr, 2010, at 23:37, Michael Foord wrote:
> On 14/04/2010 23:32, Greg Ewing wrote:
>> Michael Foord wrote:
>>> Building Python requires, I believe, the XCode development tools to be
>>> installed. Even then, building a full version of Python - with *all* the C
>>> extensions that are part
Ben Finney schrieb:
> Nick Coghlan writes:
>
>> I would be a lot happier if argparse as a standard library module just
>> followed optparse's lead here (i.e. defined '--version' only and punted
>> on the shorthand form).
>>
>> To deal with this in a backwards compatible way while remaining on the
Hi, all,
I noticed that Python 2.7 beta 1 now contains the argparse module, which
might be a good thing. The code has been cleaned up, too, compared to
the current version 1.1.
But there is still one issue with argparse; to tell the story from the
beginning:
The ArgumentParser class uses uses '
Nick Coghlan writes:
> I would be a lot happier if argparse as a standard library module just
> followed optparse's lead here (i.e. defined '--version' only and punted
> on the shorthand form).
>
> To deal with this in a backwards compatible way while remaining on the
> path to more conventional
Hi all,
what's the status of backporting PEP 3102 ? It was supposed to go into
2.6 and it seems it won't be in 2.7 either. There is an updated patch
in the tracker [1] that applies cleanly on the latest trunk and passes
all relevant tests, so unless there has been a decision against
backporting it
Tobias Herp wrote:
> *Before Python 2.7 reaches productivity stage*, IMNSHO the following
> changes should be applied to argparse.py:
>
> - removal of the deprecation warnings
> - removal of the default usage of '-v'
> with the version information facility
>
> This is a very simple thing to do;
Hi, all,
(I don't know whether the first attempt to post this went through; I
could'nt find it, so I retry. My apologies for any inconvenience...)
I noticed that Python 2.7 beta 1 now contains the argparse module, which
might be a good thing. The code has been cleaned up, too, compared to
the c
51 matches
Mail list logo
