From 4752e4e64d67b020532f37e71e6038ade6b5a17f Mon Sep 17 00:00:00 2001 From: Greg Kiar Date: Tue, 13 Mar 2018 12:34:07 -0400 Subject: [PATCH] added clarity for includes in MANIFEST files --- non-code-files.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/non-code-files.rst b/non-code-files.rst index b6ab3e0..1e9d2a5 100644 --- a/non-code-files.rst +++ b/non-code-files.rst @@ -13,4 +13,4 @@ In order for these files to be copied at install time to the package's folder in .. note:: - Files which are to be used by your installed library (e.g. data files to support a particular computation method) should usually be placed inside of the Python module directory itself. E.g. in our case, a data file might be at ``funniest/funniest/data.json``. That way, code which loads those files can easily specify a relative path from the consuming module's ``__file__`` variable. + Files which are to be used by your installed library (e.g. data files to support a particular computation method) should usually be placed inside of the Python module directory itself. E.g. in our case, a data file might be at ``funniest/funniest/data.json``. That way, code which loads those files can easily specify a relative path from the consuming module's ``__file__`` variable. Storing this file within the module directory would require updating the `include` in the above example to be `include funniest/funniest/data.json`, correspondingly.