Hi, Brett Cannon wrote: > Now I know you said in another email that you meant for this to be ""I > would only *continue* to maintain optparse is argparse does not end up > in the standard library", but that still feels like I am being > politically pushed around and I don't like that, especially when > argparse already exists and this proposal is hypothetical. Open Source turns out to be very political unfortunately, and I'm of course driven my politics as well. I have not chosen my words carefully and I'm sorry if that causes you to think I try to push around anyone.
> Depends on how you want to do that. If you are suggesting creating > your own i18n solution that precludes gettext, then no as that is the > current solution in the standard library and you shouldn't try to > exclude it. If you want it to be pluggable enough such that gettext or > any other solution can be used, then fine. Django and Babel still use gettext without a global context, the way this would change is that you can provide your own translator when creating the option parser. > But ignoring your criteria, Armin, python-dev has the criteria that > you get commit privileges and I am not sure if you will get them > because of lack of participation on python-dev and the issue tracker. > Until you get commit privileges I can't take this seriously. I ended up with commit privileges a while ago, but don't take me serious because of that. No matter if I would have commit privileges or not, my offer is serious and I would do so either way *because* I want to see Python improve. So far I only complained about the standard library and it would only be fair to start improving it. Regards, Armin _______________________________________________ stdlib-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/stdlib-sig
