Why would you like to introduce external dependency on setuptools?

On Mon, Mar 29, 2021 at 2:54 PM John Kristensen
<issues@roundup-tracker.org> wrote:
>
>
> John Kristensen added the comment:
>
> I've attached a patch series which I think resolves the problems found in the associated issues.
>
> The first patch makes setuptools a hard dependencies for packaging/installing roundup (without the previous fallback to disutils). Using setuptools for python packaging is essentially a defacto standard these days, so I'm hoping adding setuptools as a hard dependency won't be a problem. It also includes documentation on using SOURCES.txt instead of the MANIFEST file.
>
> The second patch fixes the scripts to work with the setuptools develop command (ie. `pip install --editable .`). It is essentially just re-applying a previously reverted commit.
>
> The third patch is just removing code that is no longer needed because of the changes in the second patch.
>
> The patch series is also viewable on my github repo clone: https://github.com/roundup-tracker/roundup/compare/master...jerrykan:setuptools
>
> It might be a good idea if someone familiar with doing a release could do a quick review (particularly that the documentation is correct and the steps work) before the patches are applied.
>
> _________________________________________________
> Roundup tracker <issues@roundup-tracker.org>
> <https://issues.roundup-tracker.org/issue2550899>
> _________________________________________________