-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slide this branch forward to a place equivalent to the release of 0.10.0 #1
base: python2.6-0.9.3
Are you sure you want to change the base?
Conversation
…arse to configargparse module namespace. Enhancement bw2#9 - added constructor arg to add a 'dump config' option. Fix for bw2#14 - refactored how unknown config file options are processed. Added 'ignore_unknown_config_file_keys' constructor arg as a better-named version of the 'allow_unknown_config_file_keys' arg which is now deprecated. Enhancement bw2#15 - added 'auto_env_var_prefix' constructor arg.
Conflicts: configargparse.py
The parse_config_file and convert_parsed_args_to_config_file_contents methods were moved to a generic ConfigFileParser class, which can be overridden in the ArgumentParser constructor using the config_file_parser option. Addresses bw2#21
The very convoluted code for showing examples was greatly simplified, there is little benefit in showing true args instead of pseudo-args. For advanced parsers, the full syntax can't be expressed in a simple description, so we should also refer to the "upstream" documentation for completeness.
Support for Python2.6 (without argparse tests)
Refactor config file parsing
From https://docs.python.org/dev/library/argparse.html#dest: Any internal - characters will be converted to _ characters to make sure the string is a valid attribute name
Ensure auto_env_var_prefix converts dash to underscore like ArgParse
Here's the test I ran. First, reproduce the bug:
Then, replace py26reqs.txt in the 2nd pip call with a new file that points to this new branch instead:
The contents of the new file is…
That should match the behavior of the old branch once this is merged. |
Something is not right. Could you verify, @erikrose? Which commit did you pick up? Unfortunately, I don't have time now to investigate further - probably we could get over with this PR, but lets be absolutely sure. |
Yes, I tried to imply it above, but I wasn't clear enough. As your diff shows, the ConfigArgParse 0.10.0 release was not apparently made from the 0.10.0 tag. Instead, it seems to have been made from 0c29f30, which adds the "Programming Language :: Python :: 2.6" trove specifier and fixes the indentation of the CPython and PyPy ones. Thus, I branched from that, in order to arrive at an exact copy of the released 0.10.0 package. |
Apologies, I should have compared your fork! It looks OK:
|
Since we missed you before you went on vacation, we'll land certbot/certbot#2248 temporarily and then roll it back when you return and get a chance to land this. |
Oddly enough, the release looks to have been cut from here, not the 0.10.0 tag. This fixes certbot/certbot#2243.
Remaining to be done: