[Checkins] SVN: z3c.vcsync/trunk/ Preparing for public release.
Martijn Faassen
faassen at infrae.com
Fri May 16 16:06:34 EDT 2008
Log message for revision 86806:
Preparing for public release.
Changed:
U z3c.vcsync/trunk/CHANGES.txt
U z3c.vcsync/trunk/TODO.txt
U z3c.vcsync/trunk/setup.py
U z3c.vcsync/trunk/src/z3c/vcsync/README.txt
U z3c.vcsync/trunk/src/z3c/vcsync/conflict.txt
-=-
Modified: z3c.vcsync/trunk/CHANGES.txt
===================================================================
--- z3c.vcsync/trunk/CHANGES.txt 2008-05-16 19:51:11 UTC (rev 86805)
+++ z3c.vcsync/trunk/CHANGES.txt 2008-05-16 20:06:33 UTC (rev 86806)
@@ -75,7 +75,7 @@
* When resolving objects in the ZODB, a path was generated that has
separators that are actually dependent on the operating system in
- use (``/`` for *nix, but ``\`` for windows). This caused
+ use (``/`` for Unices, but ``\`` for windows). This caused
synchronization to fail on Windows, completely flattening
hierarchies. Now use os.path.sep to be platform-independent.
Modified: z3c.vcsync/trunk/TODO.txt
===================================================================
--- z3c.vcsync/trunk/TODO.txt 2008-05-16 19:51:11 UTC (rev 86805)
+++ z3c.vcsync/trunk/TODO.txt 2008-05-16 20:06:33 UTC (rev 86806)
@@ -1,8 +1,5 @@
-* use grokcore.component instead of grok.
+* use grokcore.component instead of grok. This now works
+ experimentally on a branch, but we're waiting for a release of Grok
+ that uses grokcore.component before we switch over.
* tests for unicode support in path names.
-
-* tests for various nasty synchronization cases with conflicts.
-
-* load optimizations - only load those objects that the version
- control system marks as new, removed, or updated, instead of everything.
Modified: z3c.vcsync/trunk/setup.py
===================================================================
--- z3c.vcsync/trunk/setup.py 2008-05-16 19:51:11 UTC (rev 86805)
+++ z3c.vcsync/trunk/setup.py 2008-05-16 20:06:33 UTC (rev 86806)
@@ -1,9 +1,20 @@
from setuptools import setup, find_packages
import sys, os
+def read(*rnames):
+ return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
+
+long_description = (
+ read('src', 'z3c', 'vcsync', 'README.txt')
+ + '\n' +
+ read('CHANGES.txt')
+ + '\n'
+ )
+
setup(name='z3c.vcsync',
version='0.12dev',
- description="Sync ZODB data with version control system, currently SVN",
+ description="Synchronize object data with a version control system",
+ long_description=long_description,
package_dir={'': 'src'},
packages=find_packages('src'),
namespace_packages=['z3c'],
@@ -12,9 +23,21 @@
install_requires=[
'setuptools',
'grok',
- 'py',
+ 'py >= 0.9.1',
],
+ license="ZPL 2.1",
entry_points="""
# -*- Entry points: -*-
""",
+ keywords = "zope3 grok web svn synchronization",
+ 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'],
)
Modified: z3c.vcsync/trunk/src/z3c/vcsync/README.txt
===================================================================
--- z3c.vcsync/trunk/src/z3c/vcsync/README.txt 2008-05-16 19:51:11 UTC (rev 86805)
+++ z3c.vcsync/trunk/src/z3c/vcsync/README.txt 2008-05-16 20:06:33 UTC (rev 86806)
@@ -159,11 +159,11 @@
and we need to add it. To do this we implement a factory (where we use
the parser for the real work)::
+ >>> from z3c.vcsync.tests import ItemFactory
+
Both parser and factory are registered per extension, in this case
``.test``. This is the name of the utility.
- >>> from z3c.vcsync.tests import ItemFactory
-
We register these components::
>>> grok.testing.grok_component('ItemSerializer', ItemSerializer)
@@ -316,5 +316,15 @@
>>> data['sub']['qux'].payload
30
+More information
+----------------
+To learn more about the APIs you can use and need to implement, see
+``interfaces.py``.
+To learn about using ``z3c.vcsync`` to import and export content, see
+``importexport.txt``.
+
+More low-level information may be gleaned from ``conflicts.txt`` and
+``internal.txt``.
+
Modified: z3c.vcsync/trunk/src/z3c/vcsync/conflict.txt
===================================================================
--- z3c.vcsync/trunk/src/z3c/vcsync/conflict.txt 2008-05-16 19:51:11 UTC (rev 86805)
+++ z3c.vcsync/trunk/src/z3c/vcsync/conflict.txt 2008-05-16 20:06:33 UTC (rev 86806)
@@ -308,6 +308,6 @@
A directory was removed in the conflict directory: should be all right
-A directory was removed in the conflict directory, but more conflicts
+XXX A directory was removed in the conflict directory, but more conflicts
created files within that directory.
More information about the Checkins
mailing list