Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:Python': 0.06; 'differently': 0.07; 'executable': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:files': 0.09; 'subject:How': 0.10; 'python': 0.11; 'thread': 0.14; 'finney': 0.16; 'libraries.': 0.16; 'protecting': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'scripts.': 0.16; 'subject:program': 0.16; 'subject:where': 0.16; 'which,': 0.16; 'files.': 0.16; 'drawing': 0.19; "python's": 0.19; 'separate': 0.22; 'shell': 0.22; 'header:User-Agent:1': 0.23; 'header:X -Complaints-To:1': 0.27; 'unix': 0.29; "i'm": 0.30; 'code': 0.31; 'libraries': 0.31; 'writes:': 0.31; 'text': 0.33; 'entirely': 0.33; 'really': 0.36; 'belong': 0.36; 'subject:data': 0.36; 'should': 0.36; 'operating': 0.37; 'ben': 0.38; 'e.g.': 0.38; 'to:addr:python-list': 0.38; 'files': 0.38; 'ability': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'according': 0.40; 'how': 0.40; 'even': 0.60; 'future': 0.60; 'ian': 0.60; 'skip:n 10': 0.64; 'skip:\xe2 10': 0.65; 'innovations': 0.68; 'attention': 0.75; 'subject:find': 0.84; 'confidence': 0.95 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ben Finney Subject: Re: How to find where data files are installed for my Python program Date: Mon, 28 Oct 2013 10:31:35 +1100 References: <00704f33-7e7f-4ccf-b28b-69776d2e237d@googlegroups.com> <526C7FEF.7020206@islandtraining.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: rasputin.madmonks.org X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-gpg.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:q2Wklj4tVaqBtWcjDltQfdeMmxM= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 26 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1382916905 news.xs4all.nl 15913 [2001:888:2000:d::a6]:51125 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:57774 Ian Kelly writes: > I don't see why Python files should be treated any differently than > other non-binary executables, e.g. shell scripts. It is an unfortunate artefact of Unix history that “binary” has an established connotation of “executable”, encompassing even executable text files. So the separation I'm drawing attention to in the FHS has nothing to do with whether the files are text files, and everything to do with whether they're executable programs and code libraries. According to the FHS (with which, of course, not every operating system is bound to conform), executable program libraries belong in an entirely separate location from non-executable data files. This thread is about how to best use Python's standard tools to support that separation on systems following the FHS. -- \ “If [a technology company] has confidence in their future | `\ ability to innovate, the importance they place on protecting | _o__) their past innovations really should decline.” —Gary Barnett | Ben Finney