On Jun 21, 2012 10:12 AM, "Chris McDonough" <chrism at plope.com> wrote:
> - Install "package resources", which are non-Python source files that
> happen to live in package directories.
I love this phrasing, by the way ("non-Python source files").
A pet peeve of mine is the insistence by some people that such files are
"data" and don't belong in package directories, despite the fact that if
you gave them a .py extension and added data="""...""" around them, they'd
be considered part of the code. A file's name and internal format aren't
what distinguishes code from data; it's the way it's *used* that matters.
I think "packaging" has swung the wrong way on this particular point, and
that resources and data files should be distinguished in setup.cfg, with
sysadmins *not* being given the option to muck about with resources --
especially not to install them in locations where they might be mistaken
for something editable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120621/de08dd54/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4