'download-cache' option should create a path if necessary
Bug #328707 reported by
Tim Molendijk
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
Confirmed
|
Low
|
Unassigned |
Bug Description
Buildout fails if the 'download-cache' option specifies a non-existent path. It does not create it if necessary, nor does it give one of its parts a chance to do so. This is not a problem if we want a shared system path the be the download cache, but if we want to use a local private download cache (i.e. below ${buildout:
To post a comment you must log in.
This causes problems not only for caches under the buildout itself, but even for more modest attempts to avoid hours of repeated downloads, like setting the download directory to ~/.buildout/cache to mirror the way that buildout treats ~/.buildout/eggs.