On 11/20/2012 09:35 PM, Jim Jewett wrote:
Aside from the new flag in distutils, the site module should automatically look into ./python_modules , as if it were a second USER_SITE. As opposed to just putting them a layer up, and looking into the application package's own directory for relative imports?
Precisely, because that kind of clutters the application's root directory, especially when the number of dependencies reaches triple digits. Think of all the entries in .hgignore/.gitignore alone.
Most notably, the bundle-inside solution will* find exactly the module it shipped with, including custom patches. The versioned-packages solution will have conflicts when more than one application provides for the same dependency, but will better support independent maintenance (or at least security patches) for the 4th-party modules.
Yeah, no having automatic security updates is a definitive downside of the bundling into a local directory; but that's no different to the situation with a virtuelenv (or user-specific packages). - Philipp