Integrate support for setup.cfg declarative config into distribution about cheroot HOT 8 CLOSED

CherryPy and Cheroot seek to reach a broad audience, so I worry that requiring a very recent version of Setuptools to build CherryPy (or install from source) might limit the audience that can run it (without errors), as you mentioned in your third drawback..

More importantly, Cheroot's package environment is based on skeleton, so I'd prefer to wait until projects in general are able to accept declarative config, and then implement it first in the skeleton so as to minimize the number of places I have to make this change.

If only there were hope for PEP-518 builders (seems to be stalled for now), which would allow for a project to declare its minimum setuptools version to build, then we could cut a release which specifically declared its dependence on a particular setuptools version. Or perhaps the setup script could perform that check.

So on the whole, I'm in favor... I'm just worried about timing and the impact that has on user-friendliness.

from cheroot.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from cheroot.

unstale

from cheroot.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from cheroot.

unstale

from cheroot.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from cheroot.

TODO: add a shim for supporting a declarative config.

from cheroot.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from cheroot.