[Checkins] SVN: Sandbox/philikon/zopeproject/trunk/ Moved changelog
from ``README.txt`` into separate ``CHANGES.txt`` file.
Philipp von Weitershausen
philikon at philikon.de
Thu Sep 27 07:05:19 EDT 2007
Log message for revision 80216:
Moved changelog from ``README.txt`` into separate ``CHANGES.txt`` file.
Changed:
A Sandbox/philikon/zopeproject/trunk/CHANGES.txt
U Sandbox/philikon/zopeproject/trunk/README.txt
U Sandbox/philikon/zopeproject/trunk/setup.py
-=-
Copied: Sandbox/philikon/zopeproject/trunk/CHANGES.txt (from rev 79726, Sandbox/philikon/zopeproject/trunk/README.txt)
===================================================================
--- Sandbox/philikon/zopeproject/trunk/CHANGES.txt (rev 0)
+++ Sandbox/philikon/zopeproject/trunk/CHANGES.txt 2007-09-27 11:05:19 UTC (rev 80216)
@@ -0,0 +1,118 @@
+Changes
+=======
+
+0.4.1 (unreleased)
+------------------
+
+* Minor improvements to the ``README.txt`` file.
+
+* Updated ``var/README.txt`` in the generated sandbox. It was
+ pointing to the wrong configuration file.
+
+* Moved changelog from ``README.txt`` into separate ``CHANGES.txt``
+ file.
+
+0.4 (2007-09-15)
+----------------
+
+New features
+~~~~~~~~~~~~
+
+* Added a zdaemon controller script much like zopectl called
+ ``*package*-ctl`` (where ``*package*`` is the name of the package
+ created with zopeproject).
+
+* Added a debug script called ``*package*-debug`` that configures the
+ application and drops into an interpreter session. It is also
+ available via ``*package*-ctl debug``.
+
+* Added ``debug.ini`` which configures a WSGI middleware for
+ intercepting exceptions and live debugging (either using Paste's
+ evalexception middleware or the Python debugger pdb_).
+
+* Added a functional test layer in ``*package*.testing`` which loads
+ the new ``ftesting.zcml``. Convenience definitions of test suites
+ pre-configured for that layer are available in ``*package*.testing``
+ as well.
+
+* More improvements to the README.txt file.
+
+Bugfixes and restructuring
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* Make use of ``zope.app.wsgi.getApplication()`` to reduce the startup
+ boiler-plate in ``startup.py`` (formerly ``application.py``).
+
+* The package that zopeproject creates is now located in a ``src``
+ directory, where it's easier to single out among the other files and
+ directories.
+
+* Fixed a bug when guessing the default eggs-directory: When
+ ~/.buildout/default.cfg did not contain an eggs-directory option,
+ zopeproject failed with a ConfigParser.NoOptionError.
+
+* Renamed ``application.py`` to ``startup.py`` to make the intent of
+ the module much clearer, and to avoid clashes with e.g. Grok (where
+ "application" means something else, and ``app.py`` is commonly used
+ for the application object).
+
+* The eggs directory will no longer be written to ``buildout.cfg`` if
+ it is the same as the buildout default in
+ ``~/.buidout/default.cfg``.
+
+* Cleaned up and enhanced the dependencies of the generated
+ application. It no longer depends on zope.app.securitypolicy, only
+ the deployment (``site.zcml``) does. Obsolete dependencies (and
+ their include statements in ZCML) have been removed.
+ ``zope.app.catalog`` and friends have been added as a convenience.
+
+0.3.2 (2007-07-17)
+------------------
+
+* If the user already has a default eggs directory set in
+ ``~/.buildout/default.cfg``, it is used as the default value for the
+ eggs directory.
+
+* Greatly improved the README.txt file.
+
+0.3.1 (2007-07-15)
+------------------
+
+* The ``buildout.cfg`` template was missing settings for the shared
+ eggs directory and thew ``newest`` flag.
+
+* Assemble the default path for the eggs directory in a
+ Windows-friendly way.
+
+0.3 (2007-07-14)
+----------------
+
+* Renamed to ``zopeproject``.
+
+* Incorporated much of the grokproject_ 0.5.x infrastructure. This
+ makes it much more robust, especially when launching zc.buildout.
+
+* Merged ``make-zope-app`` and ``deploy-zope-app`` back into one
+ command: ``zopeproject``.
+
+0.2 (2007-07-12)
+-----------------
+
+* Renamed to ``make-zope-app``.
+
+* Split ``mkzopeapp`` into two commands: ``make-zope-app`` and
+ ``deploy-zope-app``.
+
+* No longer use ``zope.paste`` for the application factory. Instead,
+ each application that's created from the skeleton defines its own
+ factory (which is reasonably small and gains flexibility).
+
+* Get rid of the ``start<<Project>>`` script. Simply use ``bin/paster
+ serve deploy.ini`` for starting the server.
+
+* Use the ``Paste#http`` server by default.
+
+0.1 (2007-07-06)
+-----------------
+
+Initial release as ``mkzopeapp``
Modified: Sandbox/philikon/zopeproject/trunk/README.txt
===================================================================
--- Sandbox/philikon/zopeproject/trunk/README.txt 2007-09-27 11:01:46 UTC (rev 80215)
+++ Sandbox/philikon/zopeproject/trunk/README.txt 2007-09-27 11:05:19 UTC (rev 80216)
@@ -363,124 +363,6 @@
login screen) or NotFound (which normally leads to an HTTP 404
response) will trigger the debugger.
-
-Changes
-=======
-
-0.4.1 (unreleased)
-------------------
-
-* Minor improvements to the README.txt file.
-
-* Updated var/README.txt in the generated sandbox. It was pointing to
- the wrong configuration file.
-
-0.4 (2007-09-15)
-----------------
-
-New features
-~~~~~~~~~~~~
-
-* Added a zdaemon controller script much like zopectl called
- ``*package*-ctl`` (where ``*package*`` is the name of the package
- created with zopeproject).
-
-* Added a debug script called ``*package*-debug`` that configures the
- application and drops into an interpreter session. It is also
- available via ``*package*-ctl debug``.
-
-* Added ``debug.ini`` which configures a WSGI middleware for
- intercepting exceptions and live debugging (either using Paste's
- evalexception middleware or the Python debugger pdb_).
-
-* Added a functional test layer in ``*package*.testing`` which loads
- the new ``ftesting.zcml``. Convenience definitions of test suites
- pre-configured for that layer are available in ``*package*.testing``
- as well.
-
-* More improvements to the README.txt file.
-
-Bugfixes and restructuring
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* Make use of ``zope.app.wsgi.getApplication()`` to reduce the startup
- boiler-plate in ``startup.py`` (formerly ``application.py``).
-
-* The package that zopeproject creates is now located in a ``src``
- directory, where it's easier to single out among the other files and
- directories.
-
-* Fixed a bug when guessing the default eggs-directory: When
- ~/.buildout/default.cfg did not contain an eggs-directory option,
- zopeproject failed with a ConfigParser.NoOptionError.
-
-* Renamed ``application.py`` to ``startup.py`` to make the intent of
- the module much clearer, and to avoid clashes with e.g. Grok (where
- "application" means something else, and ``app.py`` is commonly used
- for the application object).
-
-* The eggs directory will no longer be written to ``buildout.cfg`` if
- it is the same as the buildout default in
- ``~/.buidout/default.cfg``.
-
-* Cleaned up and enhanced the dependencies of the generated
- application. It no longer depends on zope.app.securitypolicy, only
- the deployment (``site.zcml``) does. Obsolete dependencies (and
- their include statements in ZCML) have been removed.
- ``zope.app.catalog`` and friends have been added as a convenience.
-
-0.3.2 (2007-07-17)
-------------------
-
-* If the user already has a default eggs directory set in
- ``~/.buildout/default.cfg``, it is used as the default value for the
- eggs directory.
-
-* Greatly improved the README.txt file.
-
-0.3.1 (2007-07-15)
-------------------
-
-* The ``buildout.cfg`` template was missing settings for the shared
- eggs directory and thew ``newest`` flag.
-
-* Assemble the default path for the eggs directory in a
- Windows-friendly way.
-
-0.3 (2007-07-14)
-----------------
-
-* Renamed to ``zopeproject``.
-
-* Incorporated much of the grokproject_ 0.5.x infrastructure. This
- makes it much more robust, especially when launching zc.buildout.
-
-* Merged ``make-zope-app`` and ``deploy-zope-app`` back into one
- command: ``zopeproject``.
-
-0.2 (2007-07-12)
------------------
-
-* Renamed to ``make-zope-app``.
-
-* Split ``mkzopeapp`` into two commands: ``make-zope-app`` and
- ``deploy-zope-app``.
-
-* No longer use ``zope.paste`` for the application factory. Instead,
- each application that's created from the skeleton defines its own
- factory (which is reasonably small and gains flexibility).
-
-* Get rid of the ``start<<Project>>`` script. Simply use ``bin/paster
- serve deploy.ini`` for starting the server.
-
-* Use the ``Paste#http`` server by default.
-
-0.1 (2007-07-06)
------------------
-
-Initial release as ``mkzopeapp``
-
-
Reporting bugs or asking questions about zopeproject
====================================================
Modified: Sandbox/philikon/zopeproject/trunk/setup.py
===================================================================
--- Sandbox/philikon/zopeproject/trunk/setup.py 2007-09-27 11:01:46 UTC (rev 80215)
+++ Sandbox/philikon/zopeproject/trunk/setup.py 2007-09-27 11:05:19 UTC (rev 80216)
@@ -1,5 +1,9 @@
from setuptools import setup, find_packages
+long_description = (open('README.txt').read() +
+ '\n\n' +
+ open('CHANGES.txt').read())
+
setup(
name='zopeproject',
version='0.4.1dev',
@@ -9,7 +13,7 @@
download_url='svn://svn.zope.org/repos/main/Sandbox/philikon/zopeproject/trunk#egg=zopeproject-dev',
description='Tools and scripts for creating development sandboxes for '
'web applications that primarily use Zope',
- long_description=open('README.txt').read(),
+ long_description=long_description,
license='ZPL',
classifiers=['Environment :: Console',
'Intended Audience :: Developers',
More information about the Checkins
mailing list