Fix up the package meta-data and get ready for a new release.

CHANGES.txt

@@ -1,24 +1,28 @@
-============================
-Changes for z3c.viewtemplate
-============================
+=======
+CHANGES
+=======
 
+0.3.2 (2007-11-01)
+------------------
 
-Version 0.3.1 (2007-10-31)
-========================
+- Fix package meta-data.
 
-- bugfix: options did not get passed in to macro templates
+0.3.1 (2007-10-31)
+------------------
 
+- Bugfix: Options did not get passed in to macro templates.
 
-Version 0.3.0 (2007-09-27)
-========================
 
-- Add the request to BeforeUpdateEvent, this requires a recent
+0.3.0 (2007-09-27)
+------------------
+
+- Add the request to ``BeforeUpdateEvent``, this requires a recent
   zope.contentprovider package.
 
-- no dev release anymore
+- No dev release anymore.
 
 
-Version 0.2 (2007-05-01)
-========================
+0.2 (2007-05-01)
+----------------
 
-- Fire a BeforeUpdateEvent in the base views. This requires zope 3.4
+- Fire a ``BeforeUpdateEvent`` in the base views. This requires zope 3.4.

README.txt

@@ -10,10 +10,10 @@ prepare data for presentation output, namely the view classes. Skins, on the
 other hand contain the resources to generate the UI, for example templates,
 images and CSS files.
 
-The problem of the existing infrastructure is that code, template and layer are all
-hardlinked in one zcml configuration directive of the view component  -- page,
-content provider, viewlet. This package separates this triplet -- code, template,
-layer -- into two pairs, code/layer and template/skin. No additional
-components are introduced, since skins and layers are physically the same
-components.
+The problem of the existing infrastructure is that code, template and layer
+are all hardlinked in one zcml configuration directive of the view component
+-- page, content provider, viewlet. This package separates this triplet --
+code, template, layer -- into two pairs, code/layer and template/skin. No
+additional components are introduced, since skins and layers are physically
+the same components.
 

buildout.cfg

@@ -1,11 +1,7 @@
 [buildout]
 develop = .
 parts = test
-versions = versions
 
 [test]
 recipe = zc.recipe.testrunner
 eggs = z3c.viewtemplate [test]
-
-[versions]
-zope.contentprovider = 3.4.0b1.dev-r75494

setup.py

@@ -1,23 +1,61 @@
-#!python
+##############################################################################
+#
+# Copyright (c) 2007 Zope Corporation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##############################################################################
+"""Setup for z3c.viewtemplate package
+
+$Id$
+"""
+import os
 from setuptools import setup, find_packages
 
-setup(name='z3c.viewtemplate',
-      version='0.3.1',
-      author = "Zope Community",
-      author_email = "zope3-dev@zope.org",
-      description = open("README.txt").read(),
-      license = "ZPL 2.1",
-      keywords = "view template zope zope3",
-      url='http://svn.zope.org/z3c.viewtemplate',
+def read(*rnames):
+    return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
 
-      zip_safe=False,
+setup(name='z3c.viewtemplate',
+      version = '0.3.2',
+      author='Zope Corporation and Contributors',
+      author_email='zope3-dev@zope.org',
+      description='View Templates',
+      long_description=(
+          read('README.txt')
+          + '\n\n' +
+          'Detailed Dcoumentation\n' +
+          '======================\n'
+          + '\n\n' +
+          read('src', 'z3c', 'viewtemplate', 'README.txt')
+          + '\n\n' +
+          read('CHANGES.txt')
+          ),
+      keywords = "zope3 view template pagetemplate macro",
+      classifiers = [
+          'Development Status :: 5 - Production/Stable',
+          'Environment :: Web Environment',
+          'Intended Audience :: Developers',
+          'License :: OSI Approved :: Zope Public License',
+          'Programming Language :: Python',
+          'Natural Language :: English',
+          'Operating System :: OS Independent',
+          'Topic :: Internet :: WWW/HTTP',
+          'Framework :: Zope3'],
+      url='http://cheeseshop.python.org/pypi/z3c.viewtemplate',
+      license='ZPL 2.1',
       packages=find_packages('src'),
-      include_package_data=True,
-      package_dir = {'':'src'},
-      namespace_packages=['z3c',],
-      extras_require = dict(test=['zope.app.testing',
-                                  'zope.testing',
-                                  ]),
+      package_dir = {'': 'src'},
+      namespace_packages=['z3c'],
+      extras_require = dict(
+          test=['zope.app.testing',
+                'zope.testing',
+                ]),
       install_requires=[
           'setuptools',
           'zope.app.pagetemplate',
@@ -29,5 +67,6 @@
           'zope.publisher',
           'zope.tal',
           ],
+      include_package_data = True,
+      zip_safe = False,
       )
-

src/z3c/viewtemplate/README.txt

@@ -14,12 +14,12 @@ prepare data for presentation output, namely the view classes. Skins, on the
 other hand contain the resources to generate the UI, for example templates,
 images and CSS files.
 
-The problem of the existing infrastructure is that code, template and layer are all
-hardlinked in one zcml configuration directive of the view component  -- page,
-content provider, viewlet. This package separates this triplet -- code, template,
-layer -- into two pairs, code/layer and template/skin. No additional
-components are introduced, since skins and layers are physically the same
-components.
+The problem of the existing infrastructure is that code, template and layer
+are all hardlinked in one zcml configuration directive of the view component
+-- page, content provider, viewlet. This package separates this triplet --
+code, template, layer -- into two pairs, code/layer and template/skin. No
+additional components are introduced, since skins and layers are physically
+the same components.
 
 Before we can setup a view component using this new method, we have to first
 create a template ...
@@ -130,7 +130,7 @@ Use of macros.
   <div>macro1</div>
 
 Since it is possible to pass options to the viewlet let's prove if this
-is possible for macros as well::
+is possible for macros as well:
 
   >>> factory = TemplateFactory(macroTemplate, 'macro2', 'text/html')
   >>> print factory(view, request)(foo='bar')