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
pysetup create: ask before moving an existing setup.cfg #56544
Comments
I have both a setup.py and a setup.cfg in my package. I wanted to use |
Well, create is not update :) In its current form, create will save an existing setup.cfg as setup.cfg.old and generate a new one. The human operator will then have to merge both files if necessary. Automatically merging the old file into the new one would raise issues with respect to comments, whitespace and all that in Pythons < 3.2. The doc and help messages are probably unclear about that. |
On Jun 15, 2011, at 02:04 PM, Éric Araujo wrote:
I missed the setup.cfg.old. I think that's fine. Probably |
I find this behavior a bit awkward. Maybe we should ask first if it's ok to create a new setup.cfg and rename the old one, *before* doing it. |
Agreed, if “yes” is the default answer. |
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: