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 paul.moore
Recipients alexis, eric.araujo, erik.bray, jkloth, paul.moore, tarek
Date 2011-11-15.19:27:12
SpamBayes Score 2.2574856e-07
Marked as misclassified No
Message-id <CACac1F-mPKkL=Q2YWKD=d2VXzzrWGNxZOC_04UE1khOXO0hfwg@mail.gmail.com>
In-reply-to <1321378051.04.0.391182679832.issue11805@psf.upfronthosting.co.za>
Content
One important point - in the "new world" where data files living
alongside code is unsupported, the bdist_msi and bdist_wininst
installers need to be updated to install data files as needed. This
may work already (I'll do some tests to see how well when I get back
to my PC with dev builds on it) but right now bdist_wininst for
example does not support the full generality of the resource mechanism
(and it's not clear to me how it can be made to...) so there will be
restrictions on what can be allowed until the wininst format is
updated.

For installs from source, the suggested "new world" is fine. But
without a binary install process that's as flexible as a source
install, the current "alongside the code" approach has the benefit of
working well with the existing installer technology.
History
Date User Action Args
2011-11-15 19:27:13paul.mooresetrecipients: + paul.moore, tarek, jkloth, eric.araujo, alexis, erik.bray
2011-11-15 19:27:12paul.moorelinkissue11805 messages
2011-11-15 19:27:12paul.moorecreate