homepage

> 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...?