[Checkins] SVN: z3c.recipe.dev/trunk/ Fix meta data and docs. Get
ready for release.
Stephan Richter
srichter at cosmos.phy.tufts.edu
Thu Jan 24 23:12:53 EST 2008
Log message for revision 83219:
Fix meta data and docs. Get ready for release.
Changed:
U z3c.recipe.dev/trunk/CHANGES.txt
U z3c.recipe.dev/trunk/setup.py
U z3c.recipe.dev/trunk/src/z3c/recipe/dev/README.txt
U z3c.recipe.dev/trunk/src/z3c/recipe/dev/tests.py
-=-
Modified: z3c.recipe.dev/trunk/CHANGES.txt
===================================================================
--- z3c.recipe.dev/trunk/CHANGES.txt 2008-01-25 03:53:58 UTC (rev 83218)
+++ z3c.recipe.dev/trunk/CHANGES.txt 2008-01-25 04:12:52 UTC (rev 83219)
@@ -2,13 +2,13 @@
CHANGES
=======
-0.5.1 (unreleased)
+0.5.1 (2008-01-24)
------------------
-* ...
+- Bug: Correct and update meta-data.
-Version 0.5.0 (2007-01-21)
---------------------------
+0.5.0 (2008-01-21)
+------------------
- Initial Release
Modified: z3c.recipe.dev/trunk/setup.py
===================================================================
--- z3c.recipe.dev/trunk/setup.py 2008-01-25 03:53:58 UTC (rev 83218)
+++ z3c.recipe.dev/trunk/setup.py 2008-01-25 04:12:52 UTC (rev 83219)
@@ -24,13 +24,18 @@
setup(
name = 'z3c.recipe.dev',
- version = '0.5.1dev',
+ version = '0.5.1',
author = 'Roger Ineichen and the Zope Community',
- author_email = 'zope3-dev at zope.org',
+ author_email = 'zope-dev at zope.org',
description = 'Zope3 development server setup recipes',
long_description=(
read('README.txt')
+ '\n\n' +
+ 'Detailed Documentation\n'
+ '**********************'
+ + '\n\n' +
+ read('src', 'z3c', 'recipe', 'dev', 'README.txt')
+ + '\n\n' +
read('CHANGES.txt')
),
license = 'ZPL 2.1',
@@ -45,7 +50,7 @@
'Operating System :: OS Independent',
'Topic :: Internet :: WWW/HTTP',
'Framework :: Zope3'],
- url = 'http://cheeseshop.python.org/pypi/z3c.recipe.dev',
+ url = 'http://pypi.python.org/pypi/z3c.recipe.dev',
packages = find_packages('src'),
include_package_data = True,
package_dir = {'':'src'},
@@ -68,5 +73,4 @@
'script = z3c.recipe.dev.script:ScriptSetup',
]
},
- dependency_links = ['http://download.zope.org/distribution'],
)
Modified: z3c.recipe.dev/trunk/src/z3c/recipe/dev/README.txt
===================================================================
--- z3c.recipe.dev/trunk/src/z3c/recipe/dev/README.txt 2008-01-25 03:53:58 UTC (rev 83218)
+++ z3c.recipe.dev/trunk/src/z3c/recipe/dev/README.txt 2008-01-25 04:12:52 UTC (rev 83219)
@@ -7,14 +7,14 @@
This Zope 3 recipes allows you to define Zope applications.
-The 'app' recipe can be used to define a Zope application. It is designed to
-work with with Zope solely from eggs. The app recipe causes a part to be
-created. The part will contain the application's zope.conf, site.zcml,
-principals.zcml and securitypolicy.zcml. This configuration files will get
-recreated during each update. Another folder called logs will get created and
-contains the access.log and z3c.log files. This log files doesn't get
-recreated. The start script itself is located in the bin folder and uses
-the configuration files from the relevant parts folder.
+The 'app' recipe can be used to define a Zope application. It is designed to
+work with with Zope solely from eggs. The app recipe causes a part to be
+created. The part will contain the application's `zope.conf`, `site.zcml`,
+`principals.zcml` and `securitypolicy.zcml`. This configuration files will get
+recreated during each update. Another folder called logs will get created and
+contains the `access.log` and `z3c.log` files. This log files doesn't get
+recreated. The start script itself is located in the bin folder and uses the
+configuration files from the relevant parts folder.
Options
@@ -64,7 +64,7 @@
... setup(name = 'demo2', install_requires='demo1')
... ''')
-We'll create a buildout.cfg file that defines our application:
+We'll create a `buildout.cfg` file that defines our application:
>>> write('buildout.cfg',
... '''
@@ -85,49 +85,49 @@
... formatter zope.exceptions.log.Formatter
... </logfile>
... </eventlog>
- ...
+ ...
... devmode on
...
- ... site.zcml =
+ ... site.zcml =
... <include package="demo1" />
... <include package="demo2" />
- ...
- ... principals.zcml =
+ ...
+ ... principals.zcml =
... <unauthenticatedPrincipal
... id="lovelybooks.anybody"
... title="Unauthenticated User"
... />
- ...
+ ...
... <unauthenticatedGroup
... id="zope.Anybody"
... title="Unauthenticated Users"
... />
- ...
+ ...
... <authenticatedGroup
... id="zope.Authenticated"
... title="Authenticated Users"
... />
- ...
+ ...
... <everybodyGroup
... id="zope.Everybody"
... title="All Users"
... />
- ...
+ ...
... <principal
... id="zope.manager"
... title="Manager"
... login="Manager"
... password="password"
... />
- ...
+ ...
... <grant
... role="zope.Manager"
... principal="zope.manager"
... />
- ...
+ ...
... securitypolicy.zcml =
... <include package="zope.app.securitypolicy" />
- ...
+ ...
... <securityPolicy
... component="zope.app.securitypolicy.zopepolicy.ZopeSecurityPolicy"
... />
@@ -136,7 +136,7 @@
... description="All users have this role implicitly" />
... <role id="zope.Manager" title="Site Manager" />
... <role id="zope.Member" title="Site Member" />
- ...
+ ...
... <!-- Replace the following directive if you don't want public access -->
... <grant permission="zope.View"
... role="zope.Anonymous"
@@ -144,12 +144,12 @@
... <grant permission="zope.app.dublincore.view"
... role="zope.Anonymous"
... />
- ...
+ ...
... <grantAll role="zope.Manager" />
- ...
+ ...
... [var]
... recipe = zc.recipe.filestorage
- ...
+ ...
... ''' % globals())
Now, Let's run the buildout and see what we get:
@@ -207,8 +207,8 @@
- zope.conf
-z3c.recipe.script
------------------
+`z3c.recipe.script`
+-------------------
The script recipe allows us to point to scripts which the recipe will install
a execute script hook for us. You can use this if you need to run a python
@@ -251,24 +251,24 @@
... print 'Hello World'
... """)
-Alos add a __init__ to the hello package:
+Alos add a `__init__` to the `hello` package:
>>> write('hello', '__init__.py', '#make package')
-We'll create a buildout.cfg file that defines our script:
+We'll create a `buildout.cfg` file that defines our script:
>>> write('buildout.cfg',
... '''
... [buildout]
... develop = hello
... parts = helloworld
- ...
+ ...
... [helloworld]
... recipe = z3c.recipe.dev:script
... eggs = hello
... module = hello.helloworld
... method = helloWorld
- ...
+ ...
... ''' % globals())
Let's run buildout again:
@@ -280,7 +280,7 @@
Installing helloworld.
Generated script '/sample-buildout/bin/helloworld'.
-And check the script again. Now we see the helloWorld method is used:
+And check the script again. Now we see the `helloWorld()` method is used:
>>> cat('bin', 'helloworld-script.py')
#!C:\Python24\python.exe
Modified: z3c.recipe.dev/trunk/src/z3c/recipe/dev/tests.py
===================================================================
--- z3c.recipe.dev/trunk/src/z3c/recipe/dev/tests.py 2008-01-25 03:53:58 UTC (rev 83218)
+++ z3c.recipe.dev/trunk/src/z3c/recipe/dev/tests.py 2008-01-25 04:12:52 UTC (rev 83219)
@@ -57,7 +57,7 @@
), ''),
(re.compile("""['"][^\n"']+z3c.recipe.dev[^\n"']*['"],"""),
"'/z3c.recipe.dev',"),
- (re.compile('#![^\n]+\n'), ''),
+ (re.compile('#![^\n]+\n'), ''),
(re.compile('-\S+-py\d[.]\d(-\S+)?.egg'),
'-pyN.N.egg',
),
@@ -70,7 +70,7 @@
setUp=setUp, tearDown=zc.buildout.testing.buildoutTearDown,
checker=checker),
)
-
+
if __name__ == '__main__':
unittest.main(defaultTest='test_suite')
More information about the Checkins
mailing list