Does gocept.download leverage the download cache?
If so, where does it put downloads?
If not, why not?
Updated by Thomas Lotze over 10 years ago
- Status changed from New to Fix committed
- % Done changed from 0 to 100
I've refactored gocept.download now on trunk to make use of zc.buildout's download utility API. This means that zc.buildout's download cache is used now. Downloaded files are currently stored in the download cache's root directory, i.e. not inside any namespace directory such as "cmmi" or "dist". This is because downloading a resource using the gocept.download recipe doesn't say anything about the purpose the resource is needed for, which is what I think namespaces are about. (I'm gladly open to discussion about this, though.)