Re: [Zope3-dev] Static Zope 3 APIDOC available!
Stephan Richter a écrit : Hi everyone, I am happy to announce that the second Foliage sprint task is completed. Julian Bonilla, Graham Stratton and I worked on the outstanding issues on creating a functional version of the APIDOC, which comes with Zope. Thanks to Jens Vagelpohl, the static APIDOC is now available at: http://apidoc.zope.org I have also uploaded a TGZ archive to: http://download.zope.org/distribution/static-apidoc.tgz I hope that this development will spark renewed interest in the tool. In the future I plan to make more packages available in APIDOC and make it work with eggs. If you are interested, please let me know! Regards, Stephan It's very useful, thanks! Is there a way to know the version number it applies to? Is there any l10n support or is it planned? Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.sendmail having dependency on zope.app.comonent
Christian Theune a écrit : Hi, Am Freitag, den 31.08.2007, 13:06 +0200 schrieb Wichert Akkerman: Is there documentation on sources anywhere? The last time I checked there was nothing that I could understand either in zope.* or on the wiki. It took me a while to understand them myself. Especially as there is some code in there that is basically not useful. I'll try to give a very short overview: Sources are designed with three concepts: - The source itself - an iterable This can return any kind of object it wants. It doesn't have to care for browser representation, encoding, ... - A way to map a value from the iterable to something that can be used for form *values* - this is called a token - A way to map a value to something that can be displayed to the user - this is called a title The last two elements are dispatched using a so called `term`. The ITitleTokenizedTerm interface contains a triple of (value, token, term). Additionally there are some lookup functions to perform the mapping between values and terms and tokens and terms. Sources that require context use a special factory: a context source binder that is called with the context and instanciates the source when it is actually used. The general design is very nice as it seperates the concerns correctly, for simple use cases it requires you to write quite a few components (3 classes most times) which is why I came up with zc.sourcefactory which basically provides a cleaner easy-to-use API for (as the name says) application developers while having the backend APIs be logically sound. Hope this helped, Christian I was still using vocabularies, but it seems interesting, thanks for the explanation! So it basically looks like a vocabulary, with the token and title parts being seperated and optional. Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/ccomb%40free.fr ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] template path unicode bug in zcml
Hello, I've found a small bug related to zcml parsing, I would like to know if this is already known or maybe fixed in 3.4, or if this is just a configuration problem in my instance: my instance is located in a path containing some unicode char, and when I use a template= attribute in a browser:page attribute, I get a ascii decode error while the zcml parser tries to build the path of the template file. Christophe (...) args = toargs(context, *self.argdata) File /usr/lib/python2.4/site-packages/zope/configuration/config.py, line 1383, in toargs args[str(name)] = field.fromUnicode(s) File /usr/lib/python2.4/site-packages/zope/configuration/fields.py, line 291, in fromUnicode return self.context.path(u) File /usr/lib/python2.4/site-packages/zope/configuration/config.py, line 256, in path return os.path.join(basepath, filename) File /usr/lib/python2.4/posixpath.py, line 65, in join path += '/' + b zope.configuration.xmlconfig.ZopeXMLConfigurationError: File ... ZopeXMLConfigurationError: File ... ZopeXMLConfigurationError: File ... ZopeXMLConfigurationError: File ... UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 28: ordinal not in range(128) ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] base href generation is wrong ?
Christophe Combelles a écrit : Hello, I'm trying to see an custom image object with a custom @@index.html The url of the object is /container/image.jpeg There is some explanation of base href usage in zope/app/file/browser/url.txt * If I visit /container/image.jpeg, I get no base href, and the edit link in my menu appears as /container/@@edit.html * If I visit /container/image.jpeg/, I get the following base href : base href=/container/image.jpeg But this has no effect on the relative links in the page, and the edit menu link still appears as: /container/@@edit.html instead of /container/image.jpeg/@@edit.html I've tried to add a slash in zope/publisher/browser.py:713, so that the generated base href is: base href=/container/image.jpeg/ And now the relative links are ok. Am I wrong or should it be fixed? It seems the problem comes from somewhere else. I'm visiting container/image.jpeg or container/image.jpeg/ and the request/getURL returns container/image.jpeg instead of container/image.jpeg/@@index.html ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] base href generation is wrong ?
Hello, I'm trying to see an custom image object with a custom @@index.html The url of the object is /container/image.jpeg There is some explanation of base href usage in zope/app/file/browser/url.txt * If I visit /container/image.jpeg, I get no base href, and the edit link in my menu appears as /container/@@edit.html * If I visit /container/image.jpeg/, I get the following base href : base href=/container/image.jpeg But this has no effect on the relative links in the page, and the edit menu link still appears as: /container/@@edit.html instead of /container/image.jpeg/@@edit.html I've tried to add a slash in zope/publisher/browser.py:713, so that the generated base href is: base href=/container/image.jpeg/ And now the relative links are ok. Am I wrong or should it be fixed? Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] namechooser : object deleted instead of being renamed
Hi, I've experienced a dangerous behaviour with namechoosers : If the namechooser computes a name which is the same as the current name, the object is deleted! This is simple to reproduce : - register a name chooser that only returns foobar - create your object → ok it's name is foobar - from the Contents view of it's container, try to rename it (with a different name) - → deleted Someone should try to reproduce that, to be sure that's not a side effect of my app, but I don't think so. Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] for attribute not checked in zcml
Hello, Many zcml directives have a for attribute, which take an interface as argument. Absent-minded people like me sometimes happen to put a real class instead of an interface in the for attributes. * On browser:page, one can put a real class with no error. Is it correct? * On browser:containerViews, that lead to a non explicit error : Error object: list.index(x): x not in list Is there a possibility to check this thing during startup, when zcml is parsed? That would save time finding out what the real problem is. Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: for attribute not checked in zcml
Martin Aspeli a écrit : Christophe Combelles wrote: Hello, Many zcml directives have a for attribute, which take an interface as argument. Absent-minded people like me sometimes happen to put a real class instead of an interface in the for attributes. * On browser:page, one can put a real class with no error. Is it correct? Yes. Browser views are just adapters, and adapters can be registered for a specific class, as well as for an interface. Think of a class as being an interface which is implemented by a single class only (itself). Does it mean I can have both a generic view for an interface, and a specific view for a particular implementation of that interface ? ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] translation of zope3
Hi, Is translations.launchpad.net the regular and recommended way of translating zope3 ? Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Blob backward compatibility
I'm also just starting working on a project (my first paid project on Zope3 \o/) that will probably include blobs, because it will store some videos (100Mo) for an extranet. Should I expect incompatible changes to happen in the next few months? Should I consider blobs now, or should I stick with some kind of extfile? Christophe btw, I'm unable to upload any file bigger than 40kB, so 100Mb looks like a dream for now... Martijn Faassen a écrit : Hey, Jim Fulton wrote: I'm finally looking closely at Blobs and making a few changes. Some of these are backward incompatible. Most are inconsequential. Since Blobs are still considered experimental, I feel fairly free to do this, but I don't want to create undue pain for people. I will make sure that the Zope 3 tests pass after the changes. Is anyone using Blobs in production? Does anyone have precious blob pickles? Not me. The reason for this note is that I do intend to start using them within the next few months. So I'm happy more work is happening on them before I run into them. :) Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/ccomb%40free.fr ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] upload 40kb impossible
Hello, I've already posted a few message on Zope3-Users. I get a weird problem on upload, using z.a.file.file. (using Zope3.3.1 with python 2.4.4). Whenever I try to upload a file larger than ~40Kb, nothing happens and I'm redirected to the same upload form I came from. After investigating, I discovered that cgi.FieldStorage does not parse entirely the HTTP stream (zope.publisher.browser.py:263), and stop in the middle of the stream. The resulting fields are: ['field.contentType', 'field.data'] instead of ['field.contentType', 'field.data', 'UPDATE_SUBMIT', 'add_input_name'] I've checked that the input stream does contain UPDATE_SUBMIT, but the resulting request.form doesn't! I've found some related bugs here: https://bugs.launchpad.net/zope3/+bug/98024 http://sourceforge.net/tracker/index.php?func=detailaid=1112549group_id=5470atid=105470 https://bugs.launchpad.net/zope3/+bug/98284 Is it a problem with Python? Zope3? A Debian patch? My Setup? Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] apidoc error
Hello, I get an error in the apidoc : http://localhost:9676/++apidoc++/Code/zope/app/container/contained/ObjectMovedEvent/index.html TypeError(_insufficientContext) Is it known, or specific to my setup? (using 3.3.1) Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Zope3-Users] Community opinion about search+filter
Adam Groszer a écrit : Hello, I'd like to ask your opinion, your experiences about searching and filtering in quite large object DBs. We need to add search and filter functions to our current app, where the user might be able to create quite _sophisticated_ filter criterias. (The app is a pure Z3 app, subject is document management) Currently we're looking at something based on catalog/indexes. As I checked the most comfortable solution would be based on hurry.query. Some questions arose: - Is it necessary/worth adding indexes on all attributes? it depends on what you need to search. You may want to index everything as a whole in each object, in which case you just need one index, based on an adapter's getsearchabletext method that returns some kind of concatenation of all attributes; or you may want to be able to search in one particular attribute, so you have to create an index for this particular attribute. The most important is deciding how is built the indices. But I think there is no problem changing the indexation method, since reindexing is just a matter of clicking on a button, and waiting a some time. - How does the index perform on modification and retrieval? not sure to understand the question. Christophe The biggest problem is that this will be our first try, so we're missing experiences and are a bit puzzled about the right solution. Certain is that moving to RDB is not an option. Thanks, ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Poll example fix
Hello in zope.app.form.browser.widgets.txt there is a Poll demo I could make it work but I had to do 2 modifications : replace content_factory=.poll.Poll with class=.poll.Poll in configure.zcml and I also had to remove: factory id=zope.app.demo.poll permission=zope.ManageContent / regards, Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] python 2.5 optimizations and Zope Catalog ?
Hello, http://wiki.python.org/moin/NeedForSpeed/Successes while reading the highlights of python 2.5, I've found that some string and unicode operations, particularly **search** operations, are a LOT faster, sometimes 25x faster! As a result, (when z3 will work on py2.5), can we expect a great improvement in the Catalog? Did someone already make some tests? regards, Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] server error in apidoc (encoding pb)
Dmitry Vasiliev a écrit : Christophe Combelles wrote: Did someone have a look on this error ? Is it a trivial thing, or a local configuration problem, or is it reproduceable? (I write in utf-8, and I put # -*- coding: utf-8 -*- in my interfaces.py) You must use unicode docstrings. The encoding declaration at the top of the module doesn't do any magic by itself but just tells Python from which encoding unicode strings can be decoded. So your module should looks like this: # -*- coding: utf-8 -*- uSome docstring text in utf-8. That's it, that was actually trivial, I forgot the 'u' :) thanks ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] server error in apidoc (encoding pb)
Did someone have a look on this error ? Is it a trivial thing, or a local
configuration problem, or is it reproduceable?
(I write in utf-8, and I put # -*- coding: utf-8 -*- in my interfaces.py)
Christophe
Christophe Combelles a écrit :
Hello,
When I put some accentuated character in the docstring of an interface
and I want to see the interface doc in
apidoc-interfaces-search-IMyInterface,
I then get a server error:
File /usr/lib/python2.4/site-packages/zope/tales/tales.py, line 696,
in evaluate
return expression(self)
- /usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt
- Line 23, Column 4
- Expression: PathExpr standard:u'view/getDoc'
- Names:
{'args': (),
'context': InterfaceClass
zblog.category.interfaces.ICategoryContainer,
'default': object object at 0xb7db0548,
'loop': {},
'nothing': None,
'options': {},
'repeat': {},
'request': zope.publisher.browser.BrowserRequest instance
URL=http://localhost:9673/++apidoc++/Interface/zblog.category.interfaces.ICategoryContainer/index.html,
'template':
zope.app.pagetemplate.viewpagetemplatefile.ViewPageTemplateFile object
at 0xb6a319ac,
'usage': zope.pagetemplate.pagetemplate.TemplateUsage object at
0xb5c3ea4c,
'view': zope.app.pagetemplate.simpleviewclass.SimpleViewClass
from /usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt
object at 0xb5c3ef4c,
'views': zope.app.pagetemplate.viewpagetemplatefile.ViewMapper
object at 0xb5bf9d6c}
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/ccomb%40free.fr
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] server error in apidoc (encoding pb)
Christophe Combelles a écrit :
When I put some accentuated character in the docstring of an interface
and I want to see the interface doc in
apidoc-interfaces-search-IMyInterface,
I then get a server error:
Here is the full backtrace:
--
2007-01-16T16:58:11 ERROR SiteError
http://localhost:9673/++apidoc++/Interface/zblog.category.interfaces.ICategory/index.html
Traceback (most recent call last):
File /usr/lib/python2.4/site-packages/zope/publisher/publish.py, line 133,
in publish
result = publication.callObject(request, obj)
File
/usr/lib/python2.4/site-packages/zope/app/publication/zopepublication.py, line
161, in callObject
return mapply(ob, request.getPositionalArguments(), request)
File /usr/lib/python2.4/site-packages/zope/publisher/publish.py, line 108,
in mapply
return debug_call(obj, args)
- __traceback_info__: security proxied
zope.app.pagetemplate.simpleviewclass.SimpleViewClass from
/usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt instance at
0xb57112cc
File /usr/lib/python2.4/site-packages/zope/publisher/publish.py, line 114,
in debug_call
return obj(*args)
File
/usr/lib/python2.4/site-packages/zope/app/pagetemplate/simpleviewclass.py,
line 44, in __call__
return self.index(*args, **kw)
File
/usr/lib/python2.4/site-packages/zope/app/pagetemplate/viewpagetemplatefile.py,
line 83, in __call__
return self.im_func(im_self, *args, **kw)
File
/usr/lib/python2.4/site-packages/zope/app/pagetemplate/viewpagetemplatefile.py,
line 51, in __call__
sourceAnnotations=getattr(debug_flags, 'sourceAnnotations', 0),
File /usr/lib/python2.4/site-packages/zope/pagetemplate/pagetemplate.py,
line 117, in pt_render
strictinsert=0, sourceAnnotations=sourceAnnotations)()
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 271,
in __call__
self.interpret(self.program)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 346,
in interpret
handlers[opcode](self, args)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 891,
in do_useMacro
self.interpret(macro)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 346,
in interpret
handlers[opcode](self, args)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 536,
in do_optTag_tal
self.do_optTag(stuff)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 521,
in do_optTag
return self.no_tag(start, program)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 516,
in no_tag
self.interpret(program)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 346,
in interpret
handlers[opcode](self, args)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 949,
in do_defineSlot
self.interpret(slot)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 346,
in interpret
handlers[opcode](self, args)
File /usr/lib/python2.4/site-packages/zope/tal/talinterpreter.py, line 745,
in do_insertStructure_tal
structure = self.engine.evaluateStructure(expr)
File /usr/lib/python2.4/site-packages/zope/tales/tales.py, line 696, in
evaluate
return expression(self)
- /usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt
- Line 23, Column 4
- Expression: PathExpr standard:u'view/getDoc'
- Names:
{'args': (),
'context': InterfaceClass zblog.category.interfaces.ICategory,
'default': object object at 0xb7dab548,
'loop': {},
'nothing': None,
'options': {},
'repeat': {},
'request': zope.publisher.browser.BrowserRequest instance
URL=http://localhost:9673/++apidoc++/Interface/zblog.category.interfaces.ICategory/index.html,
'template':
zope.app.pagetemplate.viewpagetemplatefile.ViewPageTemplateFile object at
0xb6a2c9ac,
'usage': zope.pagetemplate.pagetemplate.TemplateUsage object at
0xb5711ccc,
'view': zope.app.pagetemplate.simpleviewclass.SimpleViewClass from
/usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt object at
0xb57112cc,
'views': zope.app.pagetemplate.viewpagetemplatefile.ViewMapper object
at 0xb5711d4c}
File /usr/lib/python2.4/site-packages/zope/tales/expressions.py, line 217,
in __call__
return self._eval(econtext)
File /usr/lib/python2.4/site-packages/zope/tales/expressions.py, line 211,
in _eval
return ob()
File
/usr/lib/python2.4/site-packages/zope/app/apidoc/ifacemodule/browser.py, line
85, in getDoc
return renderText(iface.__doc__, inspect.getmodule(iface))
File /usr/lib/python2.4/site-packages/zope/app/apidoc/utilities.py, line
327, in renderText
source = createObject(format, text)
File /usr/lib/python2.4/site-packages/zope/component/_api.py, line 224, in
createObject
return getUtility(IFactory, __factory_name, context)(*args, **kwargs)
File /usr/lib
[Zope3-dev] server error in apidoc (encoding pb)
Hello,
When I put some accentuated character in the docstring of an interface
and I want to see the interface doc in apidoc-interfaces-search-IMyInterface,
I then get a server error:
File /usr/lib/python2.4/site-packages/zope/tales/tales.py, line 696, in
evaluate
return expression(self)
- /usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt
- Line 23, Column 4
- Expression: PathExpr standard:u'view/getDoc'
- Names:
{'args': (),
'context': InterfaceClass zblog.category.interfaces.ICategoryContainer,
'default': object object at 0xb7db0548,
'loop': {},
'nothing': None,
'options': {},
'repeat': {},
'request': zope.publisher.browser.BrowserRequest instance
URL=http://localhost:9673/++apidoc++/Interface/zblog.category.interfaces.ICategoryContainer/index.html,
'template':
zope.app.pagetemplate.viewpagetemplatefile.ViewPageTemplateFile object at
0xb6a319ac,
'usage': zope.pagetemplate.pagetemplate.TemplateUsage object at
0xb5c3ea4c,
'view': zope.app.pagetemplate.simpleviewclass.SimpleViewClass from
/usr/lib/zope3/lib/python/zope/app/apidoc/ifacemodule/index.pt object at
0xb5c3ef4c,
'views': zope.app.pagetemplate.viewpagetemplatefile.ViewMapper object
at 0xb5bf9d6c}
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] I wonder whether we can add README file at subversion root directory to explain how differentiate zope 2 from Zope 3 project ?
Christian Theune a écrit : Hi, KLEIN Stéphane wrote: I wonder whether we can add README file at subversion root directory to explain how differentiate zope 2 from Zope 3 project ? I suggest this content : Frequently Asked Question : Q : What directory are Zope 2 and Zope 3 projects ? A : There aren't simple rules. First, every directory that begins with Products. is a Zope 2 project. Every directory that begins with z3c or zc is a Zope 3 project. For every other directory, you have to look at its files. If there are files with zcml extension then it's a Zope 3 project. Otherwise read the README file to see if it's a Zope 2 or a Zope 3 project I this should go into the developer guidelines/SVN area in the wiki. some thoughts The problem is there is (unless unkown to me) no central description web site for all these components. Everything is in a deep svn hierarchy, and there is no way to know which one is in a finished or usable state, which one is deprecated, which one is for zope2 or zope3, etc. So when we want to find a component, we end up in http://svn.zope.org and there is no information. Such a Readme file would be at least the very beginning of a documentation for these components, or at least a way to diffentiate them. Today I found a message from early 2005 speaking about the problem with zope3 communication, presentation and documentation. http://faassen.n--tree.net/blog/view/weblog/2005/04/06/0 Nothing has changed and today there is absolutely nothing to nicely present Zope3 apart from the complicated and multiples wikis. However it seems that the eggification has brought some standard files such as CHANGES.txt INSTALL.txt MANIFEST.in README.txt Maybe it would be possible to use these files, and maybe to add a few others, to automatically generate a nice web site with the component list, their description, their state, their documentation, etc.? That way, the site would be automatically updated along with the svn when the developpers commit changes to it. Christophe ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
