This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erik.bray
Recipients alexis, eric.araujo, erik.bray, jkloth, tarek
Date 2011-11-03.18:49:07
SpamBayes Score 4.2439693e-05
Marked as misclassified No
Message-id <1320346147.83.0.477244090654.issue11805@psf.upfronthosting.co.za>
In-reply-to
Content
> When run from an uninstalled checkout, for example when developing, the 
> file will be found in the checkout.  When run after being installed on 
> a Debian system, the file will be found in /usr/local/share
> /spam/templates/log.txt.  Each Python installation can decide (through 
> sysconfig.cfg) where to install things.

Got it!  I think when I first submitted this issue my primary concern was where the resource files live in different development/deployment contexts.  Looking at sysconfig.cfg makes it all pretty clear, though it was hard to find this information a while ago.

So what exactly is the verdict then?  Keep package_data for now, but encourage resources, and dump data_files all together?  Or...?
History
Date User Action Args
2011-11-03 18:49:07erik.braysetrecipients: + erik.bray, tarek, jkloth, eric.araujo, alexis
2011-11-03 18:49:07erik.braysetmessageid: <1320346147.83.0.477244090654.issue11805@psf.upfronthosting.co.za>
2011-11-03 18:49:07erik.braylinkissue11805 messages
2011-11-03 18:49:07erik.braycreate