-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
ConfigParser to save with order #42773
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
Comments
ConfigParser saves the data in a not-predefined order. This patch orders the info to be saved in the file This patch does not let the user to specify the order. |
Logged In: YES Note that the patch is backwards (new old instead of old new). IMO the 'surgical' editing that has been proposed many times |
This patch should probably be rejected now, as patch 1371075 (which seems to be a superset of this) has been accepted. |
Closing it, because after the patch 1371075, you can control ConfigParser behaviour regarding order. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: