[Checkins] SVN: zc.recipe.filestorage/trunk/ Get ready for final
release. I restrained myself from changing the
Stephan Richter
srichter at cosmos.phy.tufts.edu
Sat Nov 3 15:25:24 EDT 2007
Log message for revision 81450:
Get ready for final release. I restrained myself from changing the
setup. ;-)
Changed:
_U zc.recipe.filestorage/trunk/
A zc.recipe.filestorage/trunk/CHANGES.txt
U zc.recipe.filestorage/trunk/README.txt
U zc.recipe.filestorage/trunk/setup.py
-=-
Property changes on: zc.recipe.filestorage/trunk
___________________________________________________________________
Name: svn:ignore
- develop-eggs
bin
parts
.installed.cfg
dist
+ develop-eggs
bin
parts
.installed.cfg
dist
zc.recipe.filestorage.egg-info
Added: zc.recipe.filestorage/trunk/CHANGES.txt
===================================================================
--- zc.recipe.filestorage/trunk/CHANGES.txt (rev 0)
+++ zc.recipe.filestorage/trunk/CHANGES.txt 2007-11-03 19:25:24 UTC (rev 81450)
@@ -0,0 +1,8 @@
+=======
+CHANGES
+=======
+
+1.0.0 (2007-11-03)
+------------------
+
+- Initial release.
Property changes on: zc.recipe.filestorage/trunk/CHANGES.txt
___________________________________________________________________
Name: svn:eol-style
+ native
Modified: zc.recipe.filestorage/trunk/README.txt
===================================================================
--- zc.recipe.filestorage/trunk/README.txt 2007-11-03 19:15:40 UTC (rev 81449)
+++ zc.recipe.filestorage/trunk/README.txt 2007-11-03 19:25:24 UTC (rev 81450)
@@ -1,3 +1,4 @@
+===================================
Recipe for setting up a filestorage
===================================
@@ -3,5 +4,5 @@
This recipe can be used to define a file-storage. It creates a ZConfig
file-storage database specification that can be used by other recipes to
-generate ZConfig configuration files.
+generate ZConfig configuration files.
This recipe takes an optional path option. If none is given, it creates and
@@ -12,7 +13,7 @@
The recipe records a zconfig option for use by other recipes.
We'll show a couple of examples, using a dictionary as a simulated buildout
-object::
+object:
>>> import zc.recipe.filestorage
>>> buildout = dict(
@@ -70,7 +71,7 @@
The update method doesn't do much, as the database part's directory
already exists, but it is present, so buildout doesn't complain and doesn't
-accidentally run install() again::
+accidentally run install() again:
>>> recipe.update()
@@ -87,15 +88,6 @@
removed in order to start the database from scratch.
-Release history
----------------
-
-1.0.0 (unreleased)
-~~~~~~~~~~~~~~~~~~
-
-Initial release.
-
-
To do
-----
Modified: zc.recipe.filestorage/trunk/setup.py
===================================================================
--- zc.recipe.filestorage/trunk/setup.py 2007-11-03 19:15:40 UTC (rev 81449)
+++ zc.recipe.filestorage/trunk/setup.py 2007-11-03 19:25:24 UTC (rev 81450)
@@ -3,16 +3,19 @@
name = "zc.recipe.filestorage"
setup(
name=name,
- version="1.0a6",
+ version="1.0.0",
author="Jim Fulton",
author_email="jim at zope.com",
description="ZC Buildout recipe for defining a file-storage",
- long_description=open("README.txt").read(),
+ long_description=(
+ open("README.txt").read()
+ + '\n\n' +
+ open("CHANGES.txt").read()),
license="ZPL 2.1",
keywords=["zodb", "zc.buildout"],
url="http://pypi.python.org/pypi/%s/" % name,
classifiers=[
- #"Development Status :: 5 - Production/Stable",
+ "Development Status :: 5 - Production/Stable",
"Framework :: ZODB",
"Framework :: Buildout",
"Intended Audience :: Developers",
@@ -21,10 +24,10 @@
"Topic :: Software Development :: Libraries :: Python Modules",
],
packages=find_packages(),
- include_package_data=True,
data_files=[(".", ["README.txt"])],
namespace_packages=["zc", "zc.recipe"],
install_requires=["zc.buildout", "zope.testing", "setuptools"],
entry_points={"zc.buildout": ["default=%s:Recipe" % name]},
+ include_package_data=True,
zip_safe=True,
)
More information about the Checkins
mailing list