Tobias Herp wrote:
>
> What /is/ this ambiguity of the "version=" argument? There is none!
>
> Do it the way optparse does it, and all is fine!
All is not fine.
How do I add a "-V" shortcut that is equivalent to "--version" as part
of an optparse program? (That's a real question, I honestly hav
Tobias Herp writes:
> (we use Python because it is convenient!),
Speak for yourself, I want no part of that "we". I use Python because
it's well defined and well documented and makes sense and provides
powerful operations and runs quickly enough in those applications
where I use it.
The fact t
"Martin v. Löwis" schrieb:
>> - 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 br
Nick Coghlan schrieb:
> Tobias Herp wrote:
>> No deprecation or removal of the simple and convenient 'version'
>> argument is needed for this. Just omit it, and build your version
>> action yourself. But please notice that there are others who appreciate
>> this simple way to do it and don't need
Nick Coghlan wrote:
> Tobias Herp wrote:
>> No deprecation or removal of the simple and convenient 'version'
>> argument is needed for this. Just omit it, and build your version
>> action yourself. But please notice that there are others who appreciate
>> this simple way to do it and don't need m
Tobias Herp wrote:
> No deprecation or removal of the simple and convenient 'version'
> argument is needed for this. Just omit it, and build your version
> action yourself. But please notice that there are others who appreciate
> this simple way to do it and don't need more.
One Obvious Way.
In
Barry Warsaw schrieb:
> 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:
>
On Mon, Apr 19, 2010 at 12:51 PM, Michael Foord
wrote:
> On 19/04/2010 21:19, Scott Dial wrote:
>> Is consensus superficial?
>
> No, but it isn't always possible or necessary. In general the maintainer of
> a module should make the best decision, not the one with the most backing.
> :-)
Yep, that
On 19/04/2010 21:19, Scott Dial wrote:
On 4/18/2010 9:44 PM, Steve Holden wrote:
Tobias Herp wrote:
Steven Bethard schrieb:
On Sun, Apr 18, 2010 at 2:35 PM, Tobias Herp wrote:
Steven Bethard schrieb:
But I'd really like a consensus about the correct b
On 4/18/2010 9:44 PM, Steve Holden wrote:
> Tobias Herp wrote:
>> Steven Bethard schrieb:
>>> On Sun, Apr 18, 2010 at 2:35 PM, Tobias Herp wrote:
Steven Bethard schrieb:
> But I'd really like a consensus about the correct behavior, and so far
> I have not seen that.
>>
>> Do you take
I'm with Martin; just let it be explicit and stick an example in the docs.
-Brett (from his phone with hopefully only one copy sent of this email)
On Apr 18, 2010 9:22 PM, Martin v. Löwis wrote:
> - many optparse programs use the version argument
> - many other programmers find this feature ver
On 19 April 2010 04:44, Ron Adam wrote:
> Note that the python interpreter uses -V and --version.
>
> r...@gutsy:~$ python3.1 -V
> Python 3.1.2
> r...@gutsy:~$ python3.1 --version
> Python 3.1.2
>
> And -v is used as follows:
>
> -v : verbose (trace import statements); also PYTHONVERBOSE=x
>
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
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
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
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
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
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
45 matches
Mail list logo
