I have both a setup.py and a setup.cfg in my package. I wanted to use `pysetup create` to add the new packaging stanzas to my setup.cfg, but instead, pysetup clobbered everything. I think it should instead append (or prepend) the new stuff to the existing file.
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: >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. I missed the setup.cfg.old. I think that's fine. Probably `create` should print a message that it moved setup.cfg to setup.cfg.old.
