[Checkins] SVN: zc.buildout/branches/tlotze-download-api/ - updated change log

Thomas Lotze tl at gocept.com
Wed Jun 3 03:27:52 EDT 2009


Log message for revision 100609:
  - updated change log
  - add new doc tests to combined doc.txt
  

Changed:
  U   zc.buildout/branches/tlotze-download-api/CHANGES.txt
  U   zc.buildout/branches/tlotze-download-api/setup.py
  U   zc.buildout/branches/tlotze-download-api/src/zc/buildout/download.txt

-=-
Modified: zc.buildout/branches/tlotze-download-api/CHANGES.txt
===================================================================
--- zc.buildout/branches/tlotze-download-api/CHANGES.txt	2009-06-03 07:25:40 UTC (rev 100608)
+++ zc.buildout/branches/tlotze-download-api/CHANGES.txt	2009-06-03 07:27:52 UTC (rev 100609)
@@ -1,7 +1,7 @@
 Change History
 **************
 
-1.2.2 (unreleased)
+1.3.0 (unreleased)
 ==================
 
 - Better Windows compatibility in test infrastructure.
@@ -14,7 +14,12 @@
   tear down as it might disturb other packages reusing buildout's
   testing infrastructure.
 
+- Added a download API that handles the download cache, offline mode etc and
+  is meant to be reused by recipes.
 
+- Used the download API to allow caching of base configurations (specified by
+  the buildout section's 'extends' option).
+
 1.2.1 (2009-03-18)
 ==================
 

Modified: zc.buildout/branches/tlotze-download-api/setup.py
===================================================================
--- zc.buildout/branches/tlotze-download-api/setup.py	2009-06-03 07:25:40 UTC (rev 100608)
+++ zc.buildout/branches/tlotze-download-api/setup.py	2009-06-03 07:27:52 UTC (rev 100609)
@@ -32,8 +32,12 @@
         + '\n' +
         read('src', 'zc', 'buildout', 'repeatable.txt')
         + '\n' +
+        read('src', 'zc', 'buildout', 'download.txt')
+        + '\n' +
         read('src', 'zc', 'buildout', 'downloadcache.txt')
         + '\n' +
+        read('src', 'zc', 'buildout', 'extends-cache.txt')
+        + '\n' +
         read('src', 'zc', 'buildout', 'setup.txt')
         + '\n' +
         read('src', 'zc', 'buildout', 'update.txt')

Modified: zc.buildout/branches/tlotze-download-api/src/zc/buildout/download.txt
===================================================================
--- zc.buildout/branches/tlotze-download-api/src/zc/buildout/download.txt	2009-06-03 07:25:40 UTC (rev 100608)
+++ zc.buildout/branches/tlotze-download-api/src/zc/buildout/download.txt	2009-06-03 07:27:52 UTC (rev 100609)
@@ -1,4 +1,3 @@
-==========================
 Using the download utility
 ==========================
 
@@ -15,7 +14,7 @@
 
 
 Downloading without using the cache
-===================================
+-----------------------------------
 
 If no download cache should be used, the download utility is instantiated
 given buildout's options and switching off the cache:
@@ -84,7 +83,7 @@
 >>> remove(path)
 
 Downloading using the download cache
-====================================
+------------------------------------
 
 In order to make use of the download cache, we need to configure the download
 utility differently. In the simplest case, we don't turn off using the cache
@@ -122,7 +121,7 @@
 /download-cache/
 
 Simple usage
-------------
+~~~~~~~~~~~~
 
 When using the cache, a file will be stored in the cache directory when it is
 first downloaded. The file system path returned by the download utility points
@@ -203,7 +202,7 @@
 >>> write(server_data, 'foo.txt', 'This is a foo text.')
 
 Using namespace sub-directories of the download cache
------------------------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 It is common to store cached copies of downloaded files within sub-directories
 of the download cache to keep some degree of order. For example, zc.buildout
@@ -257,7 +256,7 @@
 >>> write(server_data, 'foo.txt', 'This is a foo text.')
 
 Using a hash of the URL as the filename in the cache
-----------------------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 So far, the base name of the downloaded file read from the URL has been used
 for the name of the cached copy of the file. This may not be desirable in some
@@ -321,7 +320,7 @@
 
 
 Downloading with the cache being used when offline
-==================================================
+--------------------------------------------------
 
 Another way the download cache can be used is purely as a fall-back option in
 the case that a file cannot be accessed on the net, such as when a server is



More information about the Checkins mailing list