[Zope-Checkins] SVN: Zope/branches/console-scripts/ another approach for generating the console scripts through entry points
Log message for revision 96736: another approach for generating the console scripts through entry points Changed: A Zope/branches/console-scripts/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/setup.py added zpasswd
Log message for revision 96738:
added zpasswd
Changed:
U Zope/branches/console-scripts/setup.py
-=-
Modified: Zope/branches/console-scripts/setup.py
===
--- Zope/branches/console-scripts/setup.py 2009-02-19 12:46:00 UTC (rev
96737)
+++ Zope/branches/console-scripts/setup.py 2009-02-19 12:48:35 UTC (rev
96738)
@@ -264,6 +264,7 @@
entry_points={
'console_scripts' : [
'mkzopeinstance=utilities.mkzopeinstance:main',
+'zpasswd=utilities.zpasswd:main',
]
},
)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/versions-zope2.cfg ZODB3 a11 is out
Log message for revision 96739: ZODB3 a11 is out Changed: U Zope/trunk/versions-zope2.cfg -=- Modified: Zope/trunk/versions-zope2.cfg === --- Zope/trunk/versions-zope2.cfg 2009-02-19 12:48:35 UTC (rev 96738) +++ Zope/trunk/versions-zope2.cfg 2009-02-19 12:49:27 UTC (rev 96739) @@ -12,6 +12,7 @@ RestrictedPython = 3.5.0 tempstorage = 2.11.1 zLOG = 2.11.1 +ZODB3 = 3.9.0a11 zc.lockfile = 1.0 transaction = 1.0a1 zope.broken = 3.5.0 ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/src/ moved utilities to Zope2
Log message for revision 96740: moved utilities to Zope2 Changed: A Zope/branches/console-scripts/src/Zope2/utilities/ D Zope/branches/console-scripts/src/utilities/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/setup.py checkpoint for further testing
Log message for revision 96741:
checkpoint for further testing
Changed:
U Zope/branches/console-scripts/setup.py
-=-
Modified: Zope/branches/console-scripts/setup.py
===
--- Zope/branches/console-scripts/setup.py 2009-02-19 12:53:36 UTC (rev
96740)
+++ Zope/branches/console-scripts/setup.py 2009-02-19 12:55:08 UTC (rev
96741)
@@ -263,8 +263,8 @@
zip_safe=False,
entry_points={
'console_scripts' : [
-'mkzopeinstance=utilities.mkzopeinstance:main',
-'zpasswd=utilities.zpasswd:main',
+'mkzopeinstance=Zope2.utilities.mkzopeinstance:main',
+'zpasswd=Zope2.utilities.zpasswd:main',
]
},
)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py fixed detection of zopeskelsrc
Log message for revision 96743: fixed detection of zopeskelsrc Changed: U Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py -=- Modified: Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py === --- Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py 2009-02-19 13:00:24 UTC (rev 96742) +++ Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py 2009-02-19 13:11:26 UTC (rev 96743) @@ -86,7 +86,9 @@ configfile = os.path.join(instancehome, 'etc', 'zope.conf') if skelsrc is None: # default to using stock Zope skeleton source -skelsrc = os.path.join(zopehome, skel) +#skelsrc = os.path.join(zopehome, skel) +# 'utilites' dir moved to Zope2.utilities +skelsrc = os.path.join(zopehome, .., .., skel) inituser = os.path.join(instancehome, inituser) if not (user or os.path.exists(inituser)): ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/src/Zope2/utilities/instance.py added for testing (from Repoze)
Log message for revision 96744:
added for testing (from Repoze)
Changed:
A Zope/branches/console-scripts/src/Zope2/utilities/instance.py
-=-
Added: Zope/branches/console-scripts/src/Zope2/utilities/instance.py
===
--- Zope/branches/console-scripts/src/Zope2/utilities/instance.py
(rev 0)
+++ Zope/branches/console-scripts/src/Zope2/utilities/instance.py
2009-02-19 13:15:28 UTC (rev 96744)
@@ -0,0 +1,86 @@
+import optparse
+import os
+import os.path
+import sys
+import re
+
+here = os.path.abspath(os.path.dirname(__file__))
+
+# I would use string.Template, but it's just too hard to change it to
+# respect only ${brace} syntax instead of both that and $name syntax.
+TOKEN_RE = re.compile(r'\$\{([\.\w/-]+)\}')
+def rewrite(repltext, **kw):
+def replace(match):
+return kw[match.group(1)]
+return TOKEN_RE.sub(replace, repltext)
+
+def mkinstance(conf):
+sandbox = conf['sandbox']
+
+for dir in ('bin', 'etc', 'var', 'Products', 'import', 'log'):
+path = os.path.join(sandbox, dir)
+if not os.path.exists(path):
+os.makedirs(path)
+
+try:
+# this is (stupidly) required by the zdrun key in the runner
+# section of zeo.conf
+import zdaemon
+conf['zdaemon_pkgdir'] = zdaemon.__path__[0]
+except ImportError:
+conf['zdaemon_pkgdir'] = '{unknown}'
+
+zope_conf = conf['zope_conf']
+site_zcml = conf['site_zcml']
+
+for source, target in (
+('zope2.ini', 'zope2.ini'),
+(site_zcml, 'site.zcml'),
+(zope_conf, 'zope.conf'),
+('apache2.conf', 'apache2.conf'),
+('zeo.conf', 'zeo.conf'),
+):
+template = open(os.path.join(here, 'etc', source), 'r').read()
+result = rewrite(template, **conf)
+targetfile = os.path.join(sandbox, 'etc', target)
+if not os.path.exists(targetfile):
+open(targetfile, 'w').write(result)
+
+template = open(os.path.join(here, 'etc', 'zope2.wsgi'), 'r').read()
+result = rewrite(template, **conf)
+targetfile = os.path.join(sandbox, 'bin', 'zope2.wsgi')
+if not os.path.exists(targetfile):
+open(targetfile, 'w').write(result)
+os.chmod(targetfile, 0755)
+
+def main(argv=sys.argv):
+ Console script target
+parser = optparse.OptionParser(
+usage='%prog [OPTIONS]'
+)
+parser.add_option('-s', '--sandbox', action='store', dest='sandbox',
+ default='.', help='Create the instance in this
directory')
+parser.add_option('-p', '--zope-port', action='store', dest='zope_port',
+ default='8080', help='Zope HTTP port')
+parser.add_option('-j', '--zeo-port', action='store', dest='zeo_port',
+ default='8100', help='ZEO server port number')
+parser.add_option('-z', '--use-zeo', action='store_true', dest='use_zeo',
+ default=False, help='Use ZEO to house main storage')
+options, args = parser.parse_args(argv)
+try:
+# Zope 2.10+ (Five 1.5.3?+)
+from Products.Five.fivedirectives import IRegisterPackageDirective
+options.site_zcml = 'zope-2.10+-site.zcml'
+except ImportError:
+# Zope 2.9 (or Five before 1.5.3?)
+options.site_zcml = 'zope-2.9-site.zcml'
+if options.use_zeo:
+options.zope_conf = 'zope-zeoclient.conf'
+else:
+options.zope_conf = 'zope-nonzeoclient.conf'
+options.python = sys.executable
+conf = options.__dict__
+sandbox = conf['sandbox']
+conf['sandbox'] = os.path.abspath(os.path.normpath(os.path.expanduser(
+sandbox)))
+mkinstance(conf)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/s moved zopeskel to Zope2.utitilites
Log message for revision 96745: moved zopeskel to Zope2.utitilites Changed: D Zope/branches/console-scripts/skel/ U Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py A Zope/branches/console-scripts/src/Zope2/utilities/skel/ -=- Modified: Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py === --- Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py 2009-02-19 13:15:28 UTC (rev 96744) +++ Zope/branches/console-scripts/src/Zope2/utilities/mkzopeinstance.py 2009-02-19 13:18:25 UTC (rev 96745) @@ -86,9 +86,7 @@ configfile = os.path.join(instancehome, 'etc', 'zope.conf') if skelsrc is None: # default to using stock Zope skeleton source -#skelsrc = os.path.join(zopehome, skel) -# 'utilites' dir moved to Zope2.utilities -skelsrc = os.path.join(zopehome, .., .., skel) +skelsrc = os.path.join(os.path.dirname(__file__), skel) inituser = os.path.join(instancehome, inituser) if not (user or os.path.exists(inituser)): Property changes on: Zope/branches/console-scripts/src/Zope2/utilities/skel ___ Added: svn:mergeinfo + ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/setup.py omit data_files
Log message for revision 96747:
omit data_files
Changed:
U Zope/branches/console-scripts/setup.py
-=-
Modified: Zope/branches/console-scripts/setup.py
===
--- Zope/branches/console-scripts/setup.py 2009-02-19 13:27:55 UTC (rev
96746)
+++ Zope/branches/console-scripts/setup.py 2009-02-19 13:34:12 UTC (rev
96747)
@@ -44,29 +44,29 @@
packages=find_packages('src'),
package_dir={'': 'src'},
- data_files=[
-('skel', ['skel/README.txt']),
-('skel/bin', ['skel/bin/runzope.bat.in',
- 'skel/bin/runzope.in',
- 'skel/bin/zopectl.bat.in',
- 'skel/bin/zopectl.in',
- 'skel/bin/zopeservice.py.in',
- ]),
-('skel/etc', ['skel/etc/site.zcml',
- 'skel/etc/zope.conf.in',
- ]),
-('skel/etc/package-includes', []),
-('skel/Extensions', ['skel/Extensions/README.txt']),
-('skel/import', ['skel/import/README.txt',
- 'skel/import/ZopeTutorialExamples.zexp',
-]),
-('skel/lib/python', ['skel/lib/python/README.txt.in' ]),
-('skel/log', ['skel/log/README.txt']),
-('skel/Products', ['skel/Products/__init__.py',
- 'skel/Products/README.txt',
- ]),
-('skel/var', ['skel/var/README.txt']),
- ],
+# data_files=[
+#('skel', ['skel/README.txt']),
+#('skel/bin', ['skel/bin/runzope.bat.in',
+# 'skel/bin/runzope.in',
+# 'skel/bin/zopectl.bat.in',
+# 'skel/bin/zopectl.in',
+# 'skel/bin/zopeservice.py.in',
+# ]),
+#('skel/etc', ['skel/etc/site.zcml',
+# 'skel/etc/zope.conf.in',
+# ]),
+#('skel/etc/package-includes', []),
+#('skel/Extensions', ['skel/Extensions/README.txt']),
+#('skel/import', ['skel/import/README.txt',
+# 'skel/import/ZopeTutorialExamples.zexp',
+#]),
+#('skel/lib/python', ['skel/lib/python/README.txt.in' ]),
+#('skel/log', ['skel/log/README.txt']),
+#('skel/Products', ['skel/Products/__init__.py',
+# 'skel/Products/README.txt',
+# ]),
+#('skel/var', ['skel/var/README.txt']),
+# ],
ext_modules=[
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/setup.py remove data_files
Log message for revision 96748:
remove data_files
Changed:
U Zope/branches/console-scripts/setup.py
-=-
Modified: Zope/branches/console-scripts/setup.py
===
--- Zope/branches/console-scripts/setup.py 2009-02-19 13:34:12 UTC (rev
96747)
+++ Zope/branches/console-scripts/setup.py 2009-02-19 13:43:22 UTC (rev
96748)
@@ -44,30 +44,6 @@
packages=find_packages('src'),
package_dir={'': 'src'},
-# data_files=[
-#('skel', ['skel/README.txt']),
-#('skel/bin', ['skel/bin/runzope.bat.in',
-# 'skel/bin/runzope.in',
-# 'skel/bin/zopectl.bat.in',
-# 'skel/bin/zopectl.in',
-# 'skel/bin/zopeservice.py.in',
-# ]),
-#('skel/etc', ['skel/etc/site.zcml',
-# 'skel/etc/zope.conf.in',
-# ]),
-#('skel/etc/package-includes', []),
-#('skel/Extensions', ['skel/Extensions/README.txt']),
-#('skel/import', ['skel/import/README.txt',
-# 'skel/import/ZopeTutorialExamples.zexp',
-#]),
-#('skel/lib/python', ['skel/lib/python/README.txt.in' ]),
-#('skel/log', ['skel/log/README.txt']),
-#('skel/Products', ['skel/Products/__init__.py',
-# 'skel/Products/README.txt',
-# ]),
-#('skel/var', ['skel/var/README.txt']),
-# ],
-
ext_modules=[
# AccessControl
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/ auto-detect path to Zope2-egg
Log message for revision 96749:
auto-detect path to Zope2-egg
Changed:
U Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/runzope.in
U Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/zopectl.in
-=-
Modified: Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/runzope.in
===
--- Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/runzope.in
2009-02-19 13:43:22 UTC (rev 96748)
+++ Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/runzope.in
2009-02-19 14:03:12 UTC (rev 96749)
@@ -8,6 +8,7 @@
PYTHONPATH=$SOFTWARE_HOME:$PYTHONPATH
export PYTHONPATH INSTANCE_HOME SOFTWARE_HOME
-ZOPE_RUN=$SOFTWARE_HOME/Zope2/Startup/run.py
+ZOPE2PATH=`${PYTHON} -c import os, Zope2; print
os.path.dirname(Zope2.__file__) `
+ZOPE_RUN=$ZOPE2PATH/Startup/run.py
exec $PYTHON $ZOPE_RUN -C $CONFIG_FILE $@
Modified: Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/zopectl.in
===
--- Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/zopectl.in
2009-02-19 13:43:22 UTC (rev 96748)
+++ Zope/branches/console-scripts/src/Zope2/utilities/skel/bin/zopectl.in
2009-02-19 14:03:12 UTC (rev 96749)
@@ -8,6 +8,7 @@
PYTHONPATH=$SOFTWARE_HOME:$PYTHONPATH
export PYTHONPATH INSTANCE_HOME SOFTWARE_HOME
-ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
+ZOPE2PATH=`${PYTHON} -c import os, Zope2; print
os.path.dirname(Zope2.__file__) `
+ZDCTL=$ZOPE2PATH/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/buildout.cfg We don't use the omelette right now, remove!
Log message for revision 96755:
We don't use the omelette right now, remove!
Changed:
U Zope/trunk/buildout.cfg
-=-
Modified: Zope/trunk/buildout.cfg
===
--- Zope/trunk/buildout.cfg 2009-02-19 14:55:48 UTC (rev 96754)
+++ Zope/trunk/buildout.cfg 2009-02-19 14:58:34 UTC (rev 96755)
@@ -21,22 +21,6 @@
ZOPE_HOME = ${buildout:directory}
INSTANCE_HOME = ${buildout:directory}
-[omelette]
-recipe = collective.recipe.omelette = 0.7
-eggs = ${buildout:eggs}
-
-[lib_python]
-recipe = z3c.recipe.runscript
-install-script = bin/create_lib_python.py:create_lib_python
-update-script = bin/create_lib_python.py:create_lib_python
-src-dir = ${omelette:location}
-dst-dir = ${buildout:directory}/lib/python
-skip-names =
-easy_install.py
-pkg_resources.py
-setuptools
-site.py
-
[zopepy]
recipe = zc.recipe.egg
eggs = ${buildout:eggs}
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/b Removed the bin folder, as we don't use the create_lib_python script. Beware SVN will annoy you!
Log message for revision 96756:
Removed the bin folder, as we don't use the create_lib_python script. Beware
SVN will annoy you!
Changed:
D Zope/trunk/bin/
U Zope/trunk/buildout.cfg
-=-
Modified: Zope/trunk/buildout.cfg
===
--- Zope/trunk/buildout.cfg 2009-02-19 14:58:34 UTC (rev 96755)
+++ Zope/trunk/buildout.cfg 2009-02-19 15:06:31 UTC (rev 96756)
@@ -3,6 +3,7 @@
.
parts =
test
+scripts
zopepy
extends = versions-zope2.cfg
@@ -21,6 +22,10 @@
ZOPE_HOME = ${buildout:directory}
INSTANCE_HOME = ${buildout:directory}
+[scripts]
+recipe = zc.recipe.egg:scripts
+eggs = Zope2
+
[zopepy]
recipe = zc.recipe.egg
eggs = ${buildout:eggs}
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/Zope2/utilities/instance.py re-removed repoze' instance.py
Log message for revision 96757:
re-removed repoze' instance.py
Changed:
D Zope/trunk/src/Zope2/utilities/instance.py
-=-
Deleted: Zope/trunk/src/Zope2/utilities/instance.py
===
--- Zope/trunk/src/Zope2/utilities/instance.py 2009-02-19 15:06:31 UTC (rev
96756)
+++ Zope/trunk/src/Zope2/utilities/instance.py 2009-02-19 15:08:03 UTC (rev
96757)
@@ -1,86 +0,0 @@
-import optparse
-import os
-import os.path
-import sys
-import re
-
-here = os.path.abspath(os.path.dirname(__file__))
-
-# I would use string.Template, but it's just too hard to change it to
-# respect only ${brace} syntax instead of both that and $name syntax.
-TOKEN_RE = re.compile(r'\$\{([\.\w/-]+)\}')
-def rewrite(repltext, **kw):
-def replace(match):
-return kw[match.group(1)]
-return TOKEN_RE.sub(replace, repltext)
-
-def mkinstance(conf):
-sandbox = conf['sandbox']
-
-for dir in ('bin', 'etc', 'var', 'Products', 'import', 'log'):
-path = os.path.join(sandbox, dir)
-if not os.path.exists(path):
-os.makedirs(path)
-
-try:
-# this is (stupidly) required by the zdrun key in the runner
-# section of zeo.conf
-import zdaemon
-conf['zdaemon_pkgdir'] = zdaemon.__path__[0]
-except ImportError:
-conf['zdaemon_pkgdir'] = '{unknown}'
-
-zope_conf = conf['zope_conf']
-site_zcml = conf['site_zcml']
-
-for source, target in (
-('zope2.ini', 'zope2.ini'),
-(site_zcml, 'site.zcml'),
-(zope_conf, 'zope.conf'),
-('apache2.conf', 'apache2.conf'),
-('zeo.conf', 'zeo.conf'),
-):
-template = open(os.path.join(here, 'etc', source), 'r').read()
-result = rewrite(template, **conf)
-targetfile = os.path.join(sandbox, 'etc', target)
-if not os.path.exists(targetfile):
-open(targetfile, 'w').write(result)
-
-template = open(os.path.join(here, 'etc', 'zope2.wsgi'), 'r').read()
-result = rewrite(template, **conf)
-targetfile = os.path.join(sandbox, 'bin', 'zope2.wsgi')
-if not os.path.exists(targetfile):
-open(targetfile, 'w').write(result)
-os.chmod(targetfile, 0755)
-
-def main(argv=sys.argv):
- Console script target
-parser = optparse.OptionParser(
-usage='%prog [OPTIONS]'
-)
-parser.add_option('-s', '--sandbox', action='store', dest='sandbox',
- default='.', help='Create the instance in this
directory')
-parser.add_option('-p', '--zope-port', action='store', dest='zope_port',
- default='8080', help='Zope HTTP port')
-parser.add_option('-j', '--zeo-port', action='store', dest='zeo_port',
- default='8100', help='ZEO server port number')
-parser.add_option('-z', '--use-zeo', action='store_true', dest='use_zeo',
- default=False, help='Use ZEO to house main storage')
-options, args = parser.parse_args(argv)
-try:
-# Zope 2.10+ (Five 1.5.3?+)
-from Products.Five.fivedirectives import IRegisterPackageDirective
-options.site_zcml = 'zope-2.10+-site.zcml'
-except ImportError:
-# Zope 2.9 (or Five before 1.5.3?)
-options.site_zcml = 'zope-2.9-site.zcml'
-if options.use_zeo:
-options.zope_conf = 'zope-zeoclient.conf'
-else:
-options.zope_conf = 'zope-nonzeoclient.conf'
-options.python = sys.executable
-conf = options.__dict__
-sandbox = conf['sandbox']
-conf['sandbox'] = os.path.abspath(os.path.normpath(os.path.expanduser(
-sandbox)))
-mkinstance(conf)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/ No need for lib in svn either
Log message for revision 96759: No need for lib in svn either Changed: D Zope/trunk/lib/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/utilities/ No need for top-level utilities anymore, they are inside the Zope2 package now
Log message for revision 96760: No need for top-level utilities anymore, they are inside the Zope2 package now Changed: D Zope/trunk/utilities/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Externals for C headers stink
Log message for revision 96762: Externals for C headers stink Changed: U Zope/trunk/doc/INSTALL.txt _U Zope/trunk/include/ -=- Modified: Zope/trunk/doc/INSTALL.txt === --- Zope/trunk/doc/INSTALL.txt 2009-02-19 15:19:46 UTC (rev 96761) +++ Zope/trunk/doc/INSTALL.txt 2009-02-19 15:35:49 UTC (rev 96762) @@ -59,7 +59,7 @@ You will be asked to provide a user name and password for an administrator's account during ``mkzopeinstance``. To see the available -ommand-line options, run the script with the ``--help`` option:: +command-line options, run the script with the ``--help`` option:: $ bin/mkzopeinstance --help Property changes on: Zope/trunk/include ___ Modified: svn:externals - Acquisition svn://svn.zope.org/repos/main/Acquisition/trunk/src/Acquisition ExtensionClass svn://svn.zope.org/repos/main/ExtensionClass/trunk/src/ExtensionClass persistent svn://svn.zope.org/repos/main/ZODB/tags/3.9.0a10/src/persistent + Acquisition svn://svn.zope.org/repos/main/Acquisition/trunk/src/Acquisition ExtensionClass svn://svn.zope.org/repos/main/ExtensionClass/trunk/src/ExtensionClass persistent svn://svn.zope.org/repos/main/ZODB/tags/3.9.0a11/src/persistent ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/doc/CHANGES.txt ZODB 3.9.0a11
Log message for revision 96763: ZODB 3.9.0a11 Changed: U Zope/trunk/doc/CHANGES.txt -=- Modified: Zope/trunk/doc/CHANGES.txt === --- Zope/trunk/doc/CHANGES.txt 2009-02-19 15:35:49 UTC (rev 96762) +++ Zope/trunk/doc/CHANGES.txt 2009-02-19 15:41:41 UTC (rev 96763) @@ -11,7 +11,7 @@ Restructuring + -- Updated to ZODB 3.9.0a10. ZODB-level version support has been +- Updated to ZODB 3.9.0a11. ZODB-level version support has been removed and ZopeUndo now is part of Zope2. - The Zope2 SVN trunk is now a buildout pulling in all dependencies as ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/setup.py added mkzeoinstance
Log message for revision 96766:
added mkzeoinstance
Changed:
U Zope/trunk/setup.py
-=-
Modified: Zope/trunk/setup.py
===
--- Zope/trunk/setup.py 2009-02-19 15:54:53 UTC (rev 96765)
+++ Zope/trunk/setup.py 2009-02-19 16:36:36 UTC (rev 96766)
@@ -241,6 +241,7 @@
zip_safe=False,
entry_points={
'console_scripts' : [
+'mkzeoinstance=Zope2.utilities.mkzeoinstance:main',
'mkzopeinstance=Zope2.utilities.mkzopeinstance:main',
'zpasswd=Zope2.utilities.zpasswd:main',
]
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/Zope2/utilities/mkzeoinstance.py added a main() function in order to provide a proper
Log message for revision 96767: added a main() function in order to provide a proper entry point Changed: U Zope/trunk/src/Zope2/utilities/mkzeoinstance.py -=- Modified: Zope/trunk/src/Zope2/utilities/mkzeoinstance.py === --- Zope/trunk/src/Zope2/utilities/mkzeoinstance.py 2009-02-19 16:36:36 UTC (rev 96766) +++ Zope/trunk/src/Zope2/utilities/mkzeoinstance.py 2009-02-19 16:42:01 UTC (rev 96767) @@ -25,5 +25,8 @@ from ZEO.mkzeoinst import ZEOInstanceBuilder +def main(): +ZEOInstanceBuilder().run() + if __name__ == __main__: -ZEOInstanceBuilder().run() +main() ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/doc/CHANGES.txt Added a couple of known issues
Log message for revision 96791: Added a couple of known issues Changed: U Zope/trunk/doc/CHANGES.txt -=- Modified: Zope/trunk/doc/CHANGES.txt === --- Zope/trunk/doc/CHANGES.txt 2009-02-19 17:48:37 UTC (rev 96790) +++ Zope/trunk/doc/CHANGES.txt 2009-02-19 18:22:25 UTC (rev 96791) @@ -8,6 +8,18 @@ Trunk (unreleased) -- +Known issues + + +- Running Zope on Windows is not yet supported in this alpha release. + More specifically the generated startup scripts need to be adjusted, + while the code itself should work fine. + +- ZODB 3.9.0a11 does not work on Windows with Python 2.6 yet. + +- There is no old-style full tarball release that resembles the prior + releases of Zope at this point. + Restructuring + ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] zc.selenium Zope2 support
Hello, On http://svn.zope.org/zc.selenium/branches/wosc-zope2/ I've worked to make zc.selenium be usable in Zope2/Five. There are two big changes, apart from having to sprinkle some try/except imports and other small compatibility bits around: 1. Since Zope2 insists quite firmly on running in its own process, the current way reporting of test results to the runner via a thread-shared queue is not possible. Instead, I've integrated a small HTTP serving part into the runner that the browser can POST the results to. This should incur no additional overhead, since the previous way was browser POSTs to zope-side view which puts the results into the queue and now it's browser POSTs to runner-side view which puts the results into the queue. 2. I moved from class-based resources to simply use views (for *), since the Five/Zope2 machinery gave me lots of trouble that just disappeared once I switched to views instead of trying to trick resources into acting like views. I think for zc.selenium-users (who inherit from pytest.Test or use the test:seleniumTest directive) the change should be completely backward-compatible. Could someone please review the branch and check what's missing for it to be merged to the trunk? Thanks, Wolfgang -- Wolfgang Schnerring · w...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Coding style clarifications
Hi, while gathering, cleaning and consolidating the various statements that float around about the coding style for Zope 3, I found a couple of issues that I'd like to get clarification for. What I found is currently gathered at http://svn.zope.org/zope3docs/source/codingstyle/python-style.rst?rev=96729view=auto Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? Global variable names = I don't understand that rule. I kept it around because someone might be able to explain it more in-depth and whether it still applies. Import ordering === Jim proposed an alternative rule for ordering imports. Is this official? (My vote is +1 on it) Cheers, Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
Previously Christian Theune wrote: Hi, while gathering, cleaning and consolidating the various statements that float around about the coding style for Zope 3, I found a couple of issues that I'd like to get clarification for. What I found is currently gathered at http://svn.zope.org/zope3docs/source/codingstyle/python-style.rst?rev=96729view=auto Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? That would make the end result inconsistent. I seem to remember camel case being declared 'the zope standard'. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 7 OK, 1 Failed
Summary of messages to the zope-tests list. Period Wed Feb 18 12:00:00 2009 UTC to Thu Feb 19 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 18 20:59:47 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011144.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Feb 18 20:45:39 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011137.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:47:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011138.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:49:44 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011139.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:51:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011140.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:53:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011141.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 18 20:55:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011142.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:57:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011143.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Single Sign On
On Feb 19, 2009, at 2:07 AM, Marius Gedminas wrote: I have the impression that you're talking past each other. There are two ways of using OpenID: * you can be an OpenID provider, i.e. accept logins with username password and respond to authentication requests from other websites confirming that the user does own this particular OpenID. * you can be an OpenID consumer, i.e. accept OpenID URLs from users and ask the corresponding OpenID provider to validate them. It's my impression that launchpad.net is an OpenID provider only, while Shane is trying to figure out how to use the OpenID consumer API in AuthKit. I could be mistaken about any of the particular points here. I'm glad that Shane replied that what Francis said helped him. FWIW, IRT Launchpad being an OpenID consumer, that's supposed to be a possibility very soon. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Feb 19, 2009, at 5:13 AM, Wichert Akkerman wrote: Previously Christian Theune wrote: Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? That would make the end result inconsistent. I seem to remember camel case being declared 'the zope standard'. You probably remember right for some point in time at least. However, see the discussion from last year, started by this message. http://mail.zope.org/pipermail/zope3-dev/2007-August/023394.html and the decision that was apparently adopted is in this document (section titled Coding style): http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Thursday 19 February 2009, Christian Theune wrote: Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? Depends on the namespace.ZC has decisively decided to go with underscores, so all packages in the zc namespace would be like that. The zope and z3c namespace use camel-case. Global variable names = I don't understand that rule. I kept it around because someone might be able to explain it more in-depth and whether it still applies. Well, factories (most often classes) should be capitalized. Sometimes helper-functions act like classes in that they construct a new objects, then this rule suggests that it should also be capitalized. I am not sure I like that, but I can live with it. All other functions should be mixed case. Import ordering === Jim proposed an alternative rule for ordering imports. Is this official? (My vote is +1 on it) We commonly put import * before from * import *. But otherwise I agree with that rule and I started doing it this way as well. I have found the PEP8 recommendation hard to follow in certain cases, since it is subjective. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Thursday 19 February 2009, Zvezdan Petkovic wrote: and the decision that was apparently adopted is in this document (section titled Coding style): http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-soft ware.txt Except that not all people agreed to that, including me. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? According to this document in Zope3 developer info (http://wiki.zope.org/zope3/DeveloperInfo ) it is. http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt However, it seems not everybody agrees with that document completely. :-) Import ordering === Jim proposed an alternative rule for ordering imports. Is this official? (My vote is +1 on it) I like PEP-8 rule with alphabetically sorted groups. import some-python-module ... import zope.some-module ... import myapp.some-module ... It's consistent with similar import/include rules for other languages and large projects. For example, type man style on a Mac or BSD computer for BSD kernel style guide. Having said the above, I personally don't think any of the points above are so much important. For example, a single group of sorted imports (which is I think what you refer to) will still form sub-groups internally because of sorting (only without empty lines in between). The one interesting difference is that z3c.something or zc.something will sort before zope.something. Since z3c.something almost certainly depends on zope.something that looks a little out of order. Still, I don't think it's worth arguing over that difference. Similarly both method_name() and methodName() look fine to me. One could argue that mixedCase() makes public attributes visually distinct from local variables (as is suggested in http://wiki.zope.org/zope3/ZopePythonNamingConventions) . So, deviating from PEP-8 in that regard doesn't bother me at all. OTOH, there's a simplicity in following the PEP-8 single rule for any variable/attribute. Consistency is good on a coarse grain level, but once we start going into fine grain details -- whether there's a blank line in between sorted import groups or not -- it becomes unproductive. Zvezdan ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Feb 19, 2009, at 4:47 AM, Christian Theune wrote: Hi, while gathering, cleaning and consolidating the various statements that float around about the coding style for Zope 3, I found a couple of issues that I'd like to get clarification for. What I found is currently gathered at http://svn.zope.org/zope3docs/source/codingstyle/python-style.rst?rev=96729view=auto Which attribute naming is current? == Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the local consistentency rule on old code. Is that correct? This is a mess, mainly because PEP 8 changed after an alternative style had been established in the Zope community. This is complicated by the fact that many people who work on Zope projects also work on many non-zope projects. I only mention this so that readers know the history. I don't really care much about this issue. Whatever decision is made is arbitrary. Global variable names = I don't understand that rule. I kept it around because someone might be able to explain it more in-depth and whether it still applies. I don't understand it either. I think it mostly follows established Python practices which have been changing recently. I don't care much about this myself. Import ordering === Jim proposed an alternative rule for ordering imports. Is this official? (My vote is +1 on it) PEP 8's rule is silly subjective and generally a waste of time. I'm not going to waste my time following it. I sort my imports. Period. This makes from imports come before regular imports (because f comes before i). I discourage from imports, so this isn't much of an issue for me except for old code. Having imports sorted takes very little effort and makes imports easier to find and duplicated easier to spot. Grouping imports makes imports harder to maintain and read, especially since groupings are arbitrary unless they follow package boundaries, and just sorting imports groups imports by package boundaries. BTW, I strongly discourage from imports. (I didn't always have this opinion, but have seen the error of my ways. Thanks to Fred Drake for nudging me in this direction.) IMO, this is wildly more important than any of the issues raised in this thread. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Thu, Feb 19, 2009 at 11:03 AM, Jim Fulton j...@zope.com wrote: BTW, I strongly discourage from imports. (I didn't always have this opinion, but have seen the error of my ways. Thanks to Fred Drake for nudging me in this direction.) IMO, this is wildly more important than any of the issues raised in this thread. You're welcome. :-) -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Feb 19, 2009, at 11:03 AM, Jim Fulton wrote: I sort my imports. Period. This makes from imports come before regular imports (because f comes before i). I discourage from imports, so this isn't much of an issue for me except for old code. Having imports sorted takes very little effort and makes imports easier to find and duplicated easier to spot. Grouping imports makes imports harder to maintain and read, especially since groupings are arbitrary unless they follow package boundaries, and just sorting imports groups imports by package boundaries. Exactly . As I mentioned in the previous post, sorting is the *key* here. [Pun intended]. Grouping (python, zope., myapp. modules order), or non-grouping, becomes a non-issue when imports are sorted. +1 BTW, I strongly discourage from imports. (I didn't always have this opinion, but have seen the error of my ways. Thanks to Fred Drake for nudging me in this direction.) IMO, this is wildly more important than any of the issues raised in this thread. Very important for code maintenance/readability! +1 Zvezdan ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zvezdan Petkovic wrote:
On Feb 19, 2009, at 11:03 AM, Jim Fulton wrote:
I sort my imports. Period. This makes from imports come before
regular imports (because f comes before i). I discourage from
imports, so this isn't much of an issue for me except for old code.
Having imports sorted takes very little effort and makes imports
easier to find and duplicated easier to spot. Grouping imports makes
imports harder to maintain and read, especially since groupings are
arbitrary unless they follow package boundaries, and just sorting
imports groups imports by package boundaries.
Exactly . As I mentioned in the previous post, sorting is the *key*
here. [Pun intended].
Grouping (python, zope., myapp. modules order), or non-grouping,
becomes a non-issue when imports are sorted.
+1
- -1. I prefer the PEP8 grouping, where stdlib imports are separated
from dependecy imports, which are separated from local imports.
Note that this is *not* subjective (an import is unambiguously in
exaclty one of those three classifications.)
BTW, I strongly discourage from imports. (I didn't always have this
opinion, but have seen the error of my ways. Thanks to Fred Drake for
nudging me in this direction.) IMO, this is wildly more important than
any of the issues raised in this thread.
Very important for code maintenance/readability!
+1
- -1, especially in heavily-namespaced libraries: I vastly prefer from
imports to the noise of repeating the module path everywhere. A one
chearacter search ('*' or '#') normally finds the import for me, which
makes the repetition useless.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJnZpA+gerLs4ltQ4RAp3lAKDOVsZjLoWT9LmHxeY/KpXRmk+x5gCfdUmX
kx9JhthFuPgaEXokLVLo+r4=
=Vi9G
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Overhauling the Zope 2 presentation on zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, because of the failure of the new.zope.org project I would like to put the hat on for reorganizing the Zope 2 presentation on zope.org. The goal is having up some pages with the downloads, basic pointers and links with the final release of Zope 2.12 later this year. There are basically two options: create a dedicated microsite (similar to grok.zope.org) or follow the Zope 3 approach on wiki.zope.org. Unless someone provides enough resources in helping, I would like to go with the wiki approach since it is much easier to handle. Volunteers that have the same interest in Zope 2 and getting this thing done are invited to join the effort. Based on the new.zope.org experienced I am interested in effective work and not so much in interested in discussions about briefs, mission statements and other less important stuff :-) Feel free to contact me in private. Cheers, Andreas - -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: i...@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - E-Publishing, Python, Zope Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmdm8IACgkQCJIWIbr9KYzwSwCfWWTXgeM9KA+agDsKNbyHqGYQ V0YAoKahE2NBzvBWGruAjV2Fn09Zg+BD =Ra/x -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Feb 19, 2009, at 12:43 PM, Tres Seaver wrote:
Exactly . As I mentioned in the previous post, sorting is the *key*
here. [Pun intended].
Grouping (python, zope., myapp. modules order), or non-grouping,
becomes a non-issue when imports are sorted.
+1
- -1. I prefer the PEP8 grouping, where stdlib imports are
separated
from dependecy imports, which are separated from local imports.
Note that this is *not* subjective (an import is unambiguously in
exaclty one of those three classifications.)
If you read my previous post, you'll see that I also prefer PEP-8 style.
http://mail.zope.org/pipermail/zope-dev/2009-February/034629.html
What I argued and gave +1 for is that *sorting* is the most important
requirement. I explained the details in the previous post.
- -1, especially in heavily-namespaced libraries: I vastly prefer from
imports to the noise of repeating the module path everywhere. A one
chearacter search ('*' or '#') normally finds the import for me, which
makes the repetition useless.
By the character mentioned it seems you use Vim.
Arguably, one can use another key press in Vim for name completion
during typing. :-)
Seeing where the name comes from during the code review (or when
reading a diff), without having to press that key is important to some
people.
Personally, I am used to finding such things in an editor using tags,
because, for example, in C programming, one cannot use namespace
qualifiers anyway and the names can come from any other file in a
large project.
Such topics are obviously too subjective and sometimes defended too
passionately. I _tried_ to argue in my original post linked above
that such discussions are not productive. I can adapt to any style
and believe that the fine grain details should not be dogmatically
enforced but rather allow for variations in such subjective preferences.
Best regards,
Zvezdan
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Overhauling the Zope 2 presentation on zope.org
Andreas Jung wrote: because of the failure of the new.zope.org project I would like to put the hat on for reorganizing the Zope 2 presentation on zope.org. Is this failure official or is there just no action on this? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Overhauling the Zope 2 presentation on zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.02.2009 19:16 Uhr, Chris Withers wrote: Andreas Jung wrote: because of the failure of the new.zope.org project I would like to put the hat on for reorganizing the Zope 2 presentation on zope.org. Is this failure official or is there just no action on this? See this thread: http://mail.zope.org/pipermail/zope-web/2009-January/thread.html - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmdoo8ACgkQCJIWIbr9KYyYEACg43/pkq02G0GFXfQur1OJk4q7 cMMAoIkWvO1Oq/3DGkYR7eQ8fKsyVMV/ =tAsc -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
On Feb 19, 2009, at 12:43 PM, Tres Seaver wrote: - -1. I prefer the PEP8 grouping, where stdlib imports are separated from dependecy imports, which are separated from local imports. Note that this is *not* subjective (an import is unambiguously in exaclty one of those three classifications.) I find it very subjective, or, at best, orthogonal to anything I care about. If I'm working in a ZEO package, is an import from ZODB local? How about transaction? If I import asyncore or cPickle, is that coming from the standard library? It is today, but it wasn't in the past, when the code I'm reading may have been written. The grouping in PEP 8 is based on packaging decisions that are irrelevant to the meaning of the software. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
I'm with Tres on both issues: +1 for PEP-8 import grouping (sorted alphabetically within each group), -1 for repeating english.adjective.fully english.adverb.qualified english.noun.package english.noun.names all over the place in the code (this also ties with my preference of trying to keep all my names unique project-wide, for easier ctags searches). Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Overhauling the Zope 2 presentation on zope.org
Hey Andreas.. yay, thank you for taking this on. I'd like to help however I can. You asked about write access on wiki.zope.org - assuming you mean zope manager access, I've added an account for you, see private mail. (For the record, other manager accounts on wiki.zope.org at this time are: baijum, betabug, d2m, fred, jim, wheat.) I wonder if you mean to repurpose an existing wiki, start a new one, or install some new thing on the filesystem. Looking forward to finding out more. -Simon ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Coding style clarifications
Fred Drake wrote: On Thu, Feb 19, 2009 at 11:03 AM, Jim Fulton j...@zope.com wrote: BTW, I strongly discourage from imports. (I didn't always have this opinion, but have seen the error of my ways. Thanks to Fred Drake for nudging me in this direction.) IMO, this is wildly more important than any of the issues raised in this thread. You're welcome. :-) You're saying that: import zope.interface.Interface class IFoo(zope.interface.Interface): ... is better than: from zope.interface import Interface class IFoo(Interface): ... ? Shane ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Overhauling the Zope 2 presentation on zope.org
Andreas Jung wrote: See this thread: http://mail.zope.org/pipermail/zope-web/2009-January/thread.html Shame, oh well, I think dictatorship is the way to go and I think you'd make a pretty good dictator, so go for it :-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Come to the Zope Sprint @ PyCon 2009
There will be a Zope + Friends sprint @ PyCon 2009, to work on Zope and Zope-related technologies like Grok, Repoze, Deliverence etc. http://us.pycon.org/2009/sprints/projects/zope/ Because of the Repoze overlap with WSGI based frameworks we plan to work closely together with the WSGI/Pylons/TurboGears/Repoze sprint happening at the same time, so this will be a supercool webframwork sprint! Everyone is welcome! It is not necessary to sign up beforehand, but it is recommended for planning purposes. Either put your name on the wiki-page yourself, or mail me and I will add you. http://us.pycon.org/2009/sprints/projects/zope/ For general information on the sprints, see: http://us.pycon.org/2009/sprints/ or ask me. Help out / Learn / Have fun! -- Lennart Regebro http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope] Come to the Zope Sprint @ PyCon 2009
There will be a Zope + Friends sprint @ PyCon 2009, to work on Zope and Zope-related technologies like Grok, Repoze, Deliverence etc. http://us.pycon.org/2009/sprints/projects/zope/ Because of the Repoze overlap with WSGI based frameworks we plan to work closely together with the WSGI/Pylons/TurboGears/Repoze sprint happening at the same time, so this will be a supercool webframwork sprint! Everyone is welcome! It is not necessary to sign up beforehand, but it is recommended for planning purposes. Either put your name on the wiki-page yourself, or mail me and I will add you. http://us.pycon.org/2009/sprints/projects/zope/ For general information on the sprints, see: http://us.pycon.org/2009/sprints/ or ask me. Help out / Learn / Have fun! -- Lennart Regebro http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
