[Checkins] SVN: zc.async/trunk/ make it possible to make a workable sdist

[Gary Poster]

Log message for revision 89895:
  make it possible to make a workable sdist
  
  as a side effect, we get to remove the unnecessary sphinx stuff from the sdist
  (which isn't small, because of the source files for the images).
  
  small doc tweaks
  
  

Changed:
  A   zc.async/trunk/MANIFEST.in
  U   zc.async/trunk/README.txt
  U   zc.async/trunk/setup.py
  U   zc.async/trunk/src/zc/async/QUICKSTART_1_VIRTUALENV.txt

-=-
Added: zc.async/trunk/MANIFEST.in
===================================================================
--- zc.async/trunk/MANIFEST.in	                        (rev 0)
+++ zc.async/trunk/MANIFEST.in	2008-08-15 21:12:16 UTC (rev 89895)
@@ -0,0 +1,4 @@
+include src/zc/async *.txt
+exclude MANIFEST.in TEST_THIS_REST_BEFORE_REGISTERING.txt
+prune sphinx
+prune bootstrap

Modified: zc.async/trunk/README.txt
===================================================================
--- zc.async/trunk/README.txt	2008-08-15 20:57:51 UTC (rev 89894)
+++ zc.async/trunk/README.txt	2008-08-15 21:12:16 UTC (rev 89895)
@@ -1,8 +1,9 @@
 ``zc.async``
-============
+~~~~~~~~~~~~
 
+===========
 What is it?
------------
+===========
 
 The ``zc.async`` package provides **an easy-to-use Python tool that schedules
 work persistently and reliably across multiple processes and machines.**
@@ -39,8 +40,9 @@
 
 While developed as part of the Zope project, zc.async can be used stand-alone.
 
+=================
 How does it work?
------------------
+=================
 
 The system uses the Zope Object Database (ZODB), a transactional, pickle-based
 Python object database, for communication and coordination among participating

Modified: zc.async/trunk/setup.py
===================================================================
--- zc.async/trunk/setup.py	2008-08-15 20:57:51 UTC (rev 89894)
+++ zc.async/trunk/setup.py	2008-08-15 21:12:16 UTC (rev 89895)
@@ -18,6 +18,7 @@
 try:
     import docutils
 except ImportError:
+    docutils = None
     def validateReST(text):
         return ''
 else:
@@ -71,7 +72,8 @@
 
 setup(
     name='zc.async',
-    version='1.4.2a1',
+    version='1.4.2a2',
+    namespace_packages=['zc'],
     packages=find_packages('src'),
     package_dir={'':'src'},
     zip_safe=False,
@@ -81,9 +83,8 @@
         'Schedule durable tasks across multiple processes and machines.',
     long_description=text(
         'README.txt',
-        "=======\nChanges\n=======\n\n",
         'src/zc/async/CHANGES.txt',
-        out=True),
+        out=(docutils is not None)),
     license='ZPL',
     install_requires=[
         'ZODB3',
@@ -113,5 +114,4 @@
             'zope.app.component',
             'simplejson',
             ]},
-    include_package_data=True,
     )

Modified: zc.async/trunk/src/zc/async/QUICKSTART_1_VIRTUALENV.txt
===================================================================
--- zc.async/trunk/src/zc/async/QUICKSTART_1_VIRTUALENV.txt	2008-08-15 20:57:51 UTC (rev 89894)
+++ zc.async/trunk/src/zc/async/QUICKSTART_1_VIRTUALENV.txt	2008-08-15 21:12:16 UTC (rev 89895)
@@ -342,7 +342,7 @@
    We don't need these now.  But if you are really curious about ZODB
    persistence rules, here's a start.
    
-   - Anything pickleable can be persisted.  Module globals functions, can be
+   - Anything pickleable can be persisted.  Module global functions can be
      pickled (by name), for instance, and will come in handy for our examples.
    
    - Custom classes should typically inherit from persistent.Persistent.