Configure setup via setup.cfg, and refresh README content

[twidi]

No description provided.

[jdufresne]

I'm not familiar with using setup.cfg in this manner. But if it works, looks good. Just for my own curiosity, do you have docs that explain this?

[jdufresne]

I would capitalize "Django" and "Python" here as they are proper nouns.

[twidi]

Done

[twidi]

It's spme research done by @ewjoachim and myself (mainly him) when preparing our talk do PyConFR last year (you can find the slides here https://twidi.github.io/python-packaging-talk/fr still need to be translated). Maybe Joachim can give you more links than the only one I have: https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files

[jdufresne]

I see there are some docs here: https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files

Cool. Thanks for showing me this technique.

[ewjoachim]

I second what @twidi said :) I don't have a better link than the one you both shared or if you're that much into code, the PR that made it possible.

As a final note, it seems the wind keeps blowing, now towards pyproject.toml (see PEP 518), so same advantages as setup.cfg in terms of readability by a machine etc, but in a better format with better specifications. At some point, someone will merge in setuptool the possibility to do the same in pyproject.toml as can be done in setup.cfg, and then we should be stable. Maybe.

But we'll definitely be better off than with everything in setup.py.

BTW, why was this PR closed without merging ?

[twidi]

@ewjoachim sorry very very (very very) late answer but: merged because PR branch deleted before pushing master (or develop) so Github couldn't see the head of this branch (which didn't exist anymore for them) on the base branch... so marked it at closed, but really it was merged

It's an error I often make due to my git workflow but I'm trying hard to do better ;)