If you'd like to have more control over what's installed, we could re-visit the idea of adding more categories of files within distributions based on the model of "copy each category of files to a [configurable] target directory". Perhaps there could even be a "necessary" flag on each category to indicate whether the code accessed those files at runtime or not. On Thu, Apr 28, 2016 at 2:31 PM Alex Grönholm <alex.gronholm@nextday.fi> wrote:
To what end?
28.04.2016, 21:21, Barry Warsaw kirjoitti:
On Apr 27, 2016, at 10:00 PM, Alex Grönholm wrote:
The sdist should include all the source files, including tests and documentation. In binary distributions, however, they are just dead weight. Do you want the full documentation and test suites to be installed for every single dependency when you deploy your application? I sure don't.
Shouldn't that be left to the package author to decide?
-Barry
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.orghttps://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig