-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-25592: improve documentation of data_files #9767
Conversation
CC @dstufft (as suggested by https://devguide.python.org/experts/) |
Doc/distutils/setupscript.rst
Outdated
:file:`setup.py` script at the top of the package source distribution. No | ||
directory information from *files* is used to determine the final location of | ||
The *directory* should be a relative path. | ||
It is interpreted relative to the installation prefix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side note: would be nice if the reST source stayed formatted evenly (i.e. 78 chars per line, roughly?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you prefer... I don't think that's a good convention (it makes diffs messier) but I'll do it just for the sake of it.
Doc/distutils/setupscript.rst
Outdated
(Python's ``sys.prefix`` for system installations; ``site.USER_BASE`` for user installations). | ||
Each file name in *files* is interpreted relative to the | ||
:file:`setup.py` script at the top of the package source distribution. | ||
Distutils allows *directory* to be an absolute installation path, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move the sentence in the directory
description above? i.e, have two paragraphs: one describing directory
, the other describing files
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't quite follow what you were saying here, but I did organize the text in two paragraphs: the first about files
, the second about directory
.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
I have made the requested changes; please review again. |
Thanks for making the requested changes! @pitrou: please review the changes made to this pull request. |
Thanks @jdemeyer ! |
(cherry picked from commit 598e15d) Co-authored-by: jdemeyer <J.Demeyer@UGent.be>
GH-11701 is a backport of this pull request to the 3.7 branch. |
Please backport also to 2.7 |
GH-11734 is a backport of this pull request to the 2.7 branch. |
(cherry picked from commit 598e15d) Co-authored-by: jdemeyer <J.Demeyer@UGent.be>
data_files
can be installed inexec_prefix
(this is simply not true).data_files
are installed insite.USER_BASE
for user installations.https://bugs.python.org/issue25592