I would personally find it helpful if there were a document that clearly outlined the relationship between setuptools and distutils.
Specifically: does distutils provide any features that setuptools does not? I think the lack of some options, like for example the --manifest-only option to `sdist`, might be an example of this, or it may be that setuptools obsoletes this in some way that, as a newcomer, I don't yet understand. I find this a bit confusing, since it seems like the absence of such features could break installation of ported packages containing such directives in their configuration files.
So it would be helpful to either have some assurance that yes, I don't have to worry about whether or not I need to write two install scripts and a guide to porting, or to have a nice clear indication of under what circumstances I'd want to still use distutils or to write a conditional script that does certain things in certain ways depending on which package it's using.
I'm also a bit confused about how to, or if it's possible to, enable testing as part of the deployment process. This last is a bit off-topic for this venue.
Comment
I would personally find it helpful if there were a document that clearly outlined the relationship between setuptools and distutils.
Specifically: does distutils provide any features that setuptools does not? I think the lack of some options, like for example the --manifest-only option to `sdist`, might be an example of this, or it may be that setuptools obsoletes this in some way that, as a newcomer, I don't yet understand. I find this a bit confusing, since it seems like the absence of such features could break installation of ported packages containing such directives in their configuration files.
So it would be helpful to either have some assurance that yes, I don't have to worry about whether or not I need to write two install scripts and a guide to porting, or to have a nice clear indication of under what circumstances I'd want to still use distutils or to write a conditional script that does certain things in certain ways depending on which package it's using.
I'm also a bit confused about how to, or if it's possible to, enable testing as part of the deployment process. This last is a bit off-topic for this venue.