Re: [Zope3-dev] zope.fssync dependency on zope.app.file
Hi, I'm currently working on zope.fssync and zope.app.fssync. There are still some things to do (e.g. changing the API of the default file serialization adapter to read and write methods, adding security statements for serializers and deserializers). I'm planning to finish these things until 3.4. My preference would be to leave everthing as it is and include zope.fssync as a dependency and zope.app.fssync as a part of the egg. Alternatively I can try to move the code of zope.app.fssync (and zope.app.file.fssync etc.) to zope.fssync. I can live with both alternatives, of course, but in my opinion it makes sense to leave the Python API (independent of ZODB and locations etc.) in zope.fssync and the web-based API (with security and location aware pickler) in zope.app.fssync. Regards, Uwe Dr. Uwe Oestermeier Institut für Wissensmedien Knowledge Media Research Center Konrad-Adenauer-Str. 40 D-72072 Tuebingen Germany [EMAIL PROTECTED] Tel. +49 7071 979-208 Fax +49 7071 979-100 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Increment version number to 3.4dev ?
Hi, We have already incremented version number of many Zope 3 package to 3.4dev in trunk. Can I increment version number of the following packages in trunk to 3.4dev ? $ find . -name setup.py|xargs grep version=|grep -v 3.4dev ./zope.tales/setup.py: version='3.3dev', ./zope.modulealias/setup.py:version=0.1dev, ./zope.proxy/setup.py: version='3.4.0a1', ./zope.testing/setup.py:version='3.0', ./zope.exceptions/setup.py: version='3.3dev', ./zope.schema/setup.py: version='3.3dev', ./zope.dottedname/setup.py:version=0.1dev, ./zope.deprecation/setup.py:version='3.3.0', ./zope.decorator/setup.py:version=0.1dev, ./zope.documenttemplate/setup.py: version='3.3dev', ./zope.security/setup.py: version='3.3dev', ./zope.xmlpickle/setup.py: version='0.1dev', ./zope.event/setup.py:version='3.3.0', ./zope.i18n/setup.py: version='3.3dev', ./zope.testrecorder/setup.py: version='0.2', ./zope.pagetemplate/setup.py: version='3.3dev', ./zope.tal/setup.py: version='3.3dev', ./zope.thread/setup.py: version='3.3dev', ./zope.deferredimport/setup.py:version='1.0', ./zope.dublincore/setup.py:version=0.1dev, ./zope.publisher/setup.py: version='3.3dev', ./zope.sequencesort/setup.py:version=0.1dev, ./zope.structuredtext/setup.py: version='3.3dev', May be I shouldn't change zope.proxy (it is 3.4.0a1 now) ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
On 3/6/07, Baiju M [EMAIL PROTECTED] wrote: We have distributed zope.app.file with Zope 3.3 so zope.app.file should be distributed with zope.app egg when Zope 3.4 is released. And we are not distributed zope.fssync with Zope 3.3, but now zope.fssync is dependency for zope.app.file . The only dependencies I see from zope.app.file on any of the fssync stuff comes from the zope.app.file.fssync sub-package; this is intentional. The idea was that that package could be distributed separately; it should be a separate egg from zope.app.file. There are several cases of sub-packages named fssync which should be treated in this way (most of them, in fact); each of the type-specific fssync packages should depend on the package in which they are embedded and on zope.app.fssync. There should be no need to distribute any of them with a stock Zope 3.4. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
Fred Drake wrote: On 3/6/07, Baiju M [EMAIL PROTECTED] wrote: We have distributed zope.app.file with Zope 3.3 so zope.app.file should be distributed with zope.app egg when Zope 3.4 is released. And we are not distributed zope.fssync with Zope 3.3, but now zope.fssync is dependency for zope.app.file . The only dependencies I see from zope.app.file on any of the fssync stuff comes from the zope.app.file.fssync sub-package; this is intentional. The idea was that that package could be distributed separately; it should be a separate egg from zope.app.file. There are several cases of sub-packages named fssync which should be treated in this way (most of them, in fact); each of the type-specific fssync packages should depend on the package in which they are embedded and on zope.app.fssync. There should be no need to distribute any of them with a stock Zope 3.4. How can I exclude zope.app.file.fssync from zope.app package ? In zope.app, I have set zope.app.file as an svn:external, so everything under that package is included. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] z3c.ajax help
Hi all ! Could anyone help me with z3c.ajax ? I cannot find neither instructions nor examples showing how to use or deploy it. Thanks in advance ! Sixel ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
On Mar 6, 2007, at 1:31 AM, Baiju M wrote: Hi, We have distributed zope.app.file with Zope 3.3 so zope.app.file should be distributed with zope.app egg when Zope 3.4 is released. And we are not distributed zope.fssync with Zope 3.3, but now zope.fssync is dependency for zope.app.file . So I am going include zope.fssync as a dependency for zope.app package. Also since zope.fssync uses zope.app.fssync we have to include this as part of zope.app egg. Any comments ? Yes. :) Having zope.app.file.fssync as a subpackage of zope.app.file that wasn't distributed with zope.app.file was possible due to a feature in zpackage. We aren't using zpackage any more, so we can't do this any more. We need to either remove zope.app.fssync.file, or, if we think that fssync is moving along well enough, we need to move zope.app.ffile.fssync to a separate project in some namespace package, such as zope.app.filefssync. fssync is too experimental to include zope.app.file.fssync in zope.app.file. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
On Mar 6, 2007, at 3:03 AM, Uwe Oestermeier wrote: ... My preference would be to leave everthing as it is That's not possible, as we're changing out packaging technology. (See my separate note to Baiju.) and include zope.fssync as a dependency and zope.app.fssync as a part of the egg. Alternatively I can try to move the code of zope.app.fssync (and zope.app.file.fssync etc.) to zope.fssync. -1 Just move zope.app.file.fssync to it's own project. I can live with both alternatives, of course, but in my opinion it makes sense to leave the Python API (independent of ZODB and locations etc.) in zope.fssync and the web-based API (with security and location aware pickler) in zope.app.fssync. Agreed. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Increment version number to 3.4dev ?
On Mar 6, 2007, at 7:29 AM, Baiju M wrote: Hi, We have already incremented version number of many Zope 3 package to 3.4dev in trunk. Can I increment version number of the following packages in trunk to 3.4dev ? I guess. $ find . -name setup.py|xargs grep version=|grep -v 3.4dev ./zope.tales/setup.py: version='3.3dev', ./zope.modulealias/setup.py:version=0.1dev, ./zope.proxy/setup.py: version='3.4.0a1', ./zope.testing/setup.py:version='3.0', ./zope.exceptions/setup.py: version='3.3dev', ./zope.schema/setup.py: version='3.3dev', ./zope.dottedname/setup.py:version=0.1dev, ./zope.deprecation/setup.py:version='3.3.0', ./zope.decorator/setup.py:version=0.1dev, ./zope.documenttemplate/setup.py: version='3.3dev', ./zope.security/setup.py: version='3.3dev', ./zope.xmlpickle/setup.py: version='0.1dev', ./zope.event/setup.py:version='3.3.0', ./zope.i18n/setup.py: version='3.3dev', ./zope.testrecorder/setup.py: version='0.2', ./zope.pagetemplate/setup.py: version='3.3dev', ./zope.tal/setup.py: version='3.3dev', ./zope.thread/setup.py: version='3.3dev', ./zope.deferredimport/setup.py:version='1.0', ./zope.dublincore/setup.py:version=0.1dev, ./zope.publisher/setup.py: version='3.3dev', ./zope.sequencesort/setup.py:version=0.1dev, ./zope.structuredtext/setup.py: version='3.3dev', I hope this is the last time we do this. We'll end up bumping revisions number for things that haven't changed. After the 3.4 release, we'll split Zope 3 into separate projects and package revision number should only change when there is an actual change to a package. May be I shouldn't change zope.proxy (it is 3.4.0a1 now) ? Right. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
Jim Fulton [EMAIL PROTECTED] wrote: We need to either remove zope.app.fssync.file, or, if we think that fssync is moving along well enough, we need to move zope.app.ffile.fssync to a separate project in some namespace package, such as zope.app.filefssync. fssync is too experimental to include zope.app.file.fssync in zope.app.file. I agree that fssync is still experimental. The DefaultFileAdapter setBody and getBody methods, for instance, do not apply well to Blobs and other file implementations. Another problem, at least for me, is that the current implementation addresses more the use case of export/import than the use case of content management. Currently FSSync replicates the ZODB object tree in the filesystem, serializes everything into a temp file, and starts to respond after these very expensive operations. How are the chances that the response.write method is reinstated in the future? Or are there already alternatives I have missed? Given that zope.app.fssync needs more work, wouldn't it be better to move everything into one place then, e.g to zope.app.fssync.file, zope.app.fssync.zptpage etc? If the API becomes stable we still can create the separate projects. Regards, Uwe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
On Mar 6, 2007, at 9:53 AM, Uwe Oestermeier wrote: ... Given that zope.app.fssync needs more work, wouldn't it be better to move everything into one place then, e.g to zope.app.fssync.file, zope.app.fssync.zptpage etc? If the API becomes stable we still can create the separate projects. Since you're the one working on this, I'll defer to you on this detail. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.fssync dependency on zope.app.file
Jim Fulton [EMAIL PROTECTED] wrote: Since you're the one working on this, I'll defer to you on this detail. :) Ok, then I will move the things to zope.app.fssync. Uwe Dr. Uwe Oestermeier Institut für Wissensmedien Knowledge Media Research Center Konrad-Adenauer-Str. 40 D-72072 Tuebingen Germany [EMAIL PROTECTED] Tel. +49 7071 979-208 Fax +49 7071 979-100 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] i18nextract changes if you are interested.
Hello,
Using zope 3.3.0 so i18nextract may have changed.
I found that i18nextract didn't quite meet my needs.
So I changed it. The following diff shows the changes.
Basically, I wanted to allow individual py/zcml/pt
extractions to be possible.
Originally, python code is always included in an
extraction. This leads to duplication within .pot files
when there is more than one translation domain.
So a common look and feel domain stored entirely in zcml or
page templates can now be extracted without pulling
in a pile of irrelevant python messages.
The default behaviour is unchanged.
I hope you can make use of the changes. bin/i18nextract.ccrs
was the new version. Am I using diff with the arguments the
right way around? ;-)
Regards.
Mark
zope# diff bin/i18nextract.ccrs bin/i18nextract.dist
15,19d14
#
# Local modifications by Mark V. Giovannetti Mar. 6, 2007
# for the purpose of specifying python, zcml, and/or page templates
# or a combination thereof.
#
37d31
42c36
Specifies the domain that is supposed to be extracted (i.e. 'zope').
---
Specifies the domain that is supposed to be extracted (i.e. 'zope')
44c38
Specifies the package that is supposed to be searched.
---
Specifies the package that is supposed to be searched
51,70c45
May be used more than once. Does not apply to ZCML files.
Applies to python and templates only.
--python-only
Obsolete. See -c / --code If this is specified then zcml
and page templates will not be searched, depending on option
order. For example --python--only --zcml will search code
and zcml whereas --zcml --python-only will search code only
since --zcml will be overridden by --python-only.
-c / --code
Look through python code.
-z / --zcml
Look through ZCML configuration files.
-t / --pagetemplate
Look through zope page template files.
If none of -z, -t, or -c are specified then all are enabled and
all of code, zcml and page templates are searched..
If any are specified then the others default to false unless
also specified. Best not to mix them with python-only.
---
May be used more than once.
114,115c89,90
'hd:p:o:x:pczt',
['help', 'domain=', 'path=', 'python-only', 'code', 'zcml',
'pagetemplate'])
---
'hd:p:o:x:',
['help', 'domain=', 'path=', 'python-only'])
125,130d99
have_search_code = False
have_search_zcml = False
have_search_pagetemplate = False
search_code = True
search_zcml = True
search_pagetemplate = True
141,146d109
elif opt in ('-c', '--code'):
have_search_code = True
elif opt in ('-z', '--zcml'):
have_search_zcml = True
elif opt in ('-t', '--pagetemplate'):
have_search_pagetemplate = True
149,151d111
have_search_code = True
have_search_zcml = False
have_search_pagetemplate = False
164,168d123
if have_search_code or have_search_zcml or have_search_pagetemplate:
search_code = have_search_code
search_zcml = have_search_zcml
search_pagetemplate = have_search_pagetemplate
186d140
from zope.app.locales.pygettext import make_escapes
189,198c143,146
# make_escapes is still called within py_strings. If we don't call it
# here then tal_strings fails with an index error when calling escape.
make_escapes(0)
if search_code:
print Searching code.
maker.add(py_strings(path, domain, exclude=exclude_dirs), base_dir)
site_zcml = os.path.join(INSTANCE_HOME, 'etc', 'site.zcml')
if search_zcml:
print Searching ZCML.
---
maker.add(py_strings(path, domain ), base_dir)
#maker.add(py_strings(path, domain, exclude=exclude_dirs), base_dir)
if not python_only:
site_zcml = os.path.join(INSTANCE_HOME, 'etc', 'site.zcml')
200,202d147
if search_pagetemplate:
print Searching page templates.
204,208c149
if search_code or search_zcml or search_pagetemplate:
maker.write()
else:
print Nothing to search. Please see --help
---
maker.write()
--
613-947-1359
System Scientist / Scientifique, spécialiste des systèmes
Canada Centre for Remote Sensing / Centre canadien de télédéction
Natural Resources Canada, 588 Booth Street, Ottawa, Ontario, Canada, K1A 0Y7
Ressources naturelles Canada, 588 rue Booth, Ottawa, Ontario, Canada, K1A 0Y7
Government of Canada / Gouvernement du Canada
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope-dev] Re: [Zope3-dev] Google Summer of Code
On 3/5/07, Martijn Pieters [EMAIL PROTECTED] wrote: On 3/5/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Great. I've added you to http://wiki.zope.org/zope3/SummerOfCode2007. If you happen to have any project suggestions, feel free to add them to the list. I've added myself to the mentors list as well. Google will need your Google account, so I've added mine to the Wiki. -- Martijn Pieters ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
