[stdlib-sig] Maintenance of optparse

[Armin Ronacher]

Armin Ronacher wrote:
> Hi,
> 
> Michael Foord wrote:
>> That can't be a pre-requisite as we can't tell if you will succeed until
>> you actually look at the problem and see how possible it is. I would do
>> a feasibility check.
> Well assuming I succeed before feature freeze.  If I do not I failed and
> you're welcome to do whatever you want (of course including my patches
> to be part of the stdlib, but I would not continue to maintain it
> afterwards because I do not see the point then)
> 
>> * handling positional arguments including required positional arguments
>> * required options (which it looks like can be added easily - the above
>>   is less easy though)
>> * subcommands
> I can see not reason why it should not be possible to implement that in
> optparse without breaking backwards compatibility.
> 
>> That sounds good to me. I don't know how 'mandatory' others feel the use
>> of gettext is in il8n support in the standard library.
> Obviously I'm biased towards Web development where you have to keep
> everything stateless as good as possible, to allow different languages
> in the same process.  And there are good reasons why you would want to
> use optparse from inside a website (interactive shells come to mind).
> 
> I'm deeply disturbed by how the standard library is currently depending
> on global state (the locale module for example does not work at all in a
> web application).
> 
> 
> Regards,
> Armin
>