Make more use of setup.cfg

[bb-migration]

Originally reported by: Anonymous

---

Right now setuptools uses setup.cfg only for configuration options of commands, e.g.

#!python

python setup.py build_ext --inplace 

is equal to

#!python

[build_ext]
inplace=1

in setup.cfg. Why not allow users to define most of the configuration options to the setup command inside setup.cfg? It seems there was some effort done in disutils2 to allow that. As the maintainer of PyScaffold, I implemented my own logic but have a strong feeling that setuptools should directly implement this. Having a purely declarative way of defining the settings for 95% of all use cases would help beginners and intermediate Python developers a lot.

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/394

[bb-migration]

Original comment by florianwilhelm (Bitbucket: florianwilhelm, GitHub: florianwilhelm):

---

err... sorry for posting this anonymously.. I forgot to log in.

[bb-migration]

Original comment by embray (Bitbucket: embray, GitHub: embray):

---

Have you had a look at d2to1, or its progeny pbr?

[bb-migration]

Original comment by florianwilhelm (Bitbucket: florianwilhelm, GitHub: florianwilhelm):

---

@embray Thanks a lot, while d2t1 looks quite abandoned, pbr seems to do the job judging from the description. I'll check it out. But still, shouldn't this functionality be directly included into setuptools?

[bb-migration]

Original comment by embray (Bitbucket: embray, GitHub: embray):

---

Not abandoned, just no time to make updates :( pbr is better supported at the moment I think.

[jaraco]

This was released in 30.3.0.