[Zope3-dev] zope.interface category in pypi
Hi Fred, Can you add add 'Framework :: Zope3' to category here: http://cheeseshop.python.org/pypi/zope.interface Now it's not listed here: http://cheeseshop.python.org/pypi?:action=browse&c=515 May be we have to update that release? 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] Re: Grrr. zope.org wikis are evil.
Martin Aspeli wrote: Hi Jim, I have some wiki desires of my own that I'll probably never realize: - HTML WYSIWYG Wikis that don't use any form os structures text (small s) and just use an HTML editor. I think that structured text of any kind is an obstacle to Wiki use. Moin moin's markup rules drive me as batty as old Structured Text drives other people. ZWiki supports EPOZ editing and I'd love to see that used. Of course, this sort of experience avoids the need for preview or structured-text documentation. Wicked can do this, I believe, and it will likely (pending voting) be in Plone 3.0. You write ((foo)) and you get a wiki link to foo, regardless of text format. wicked is a bit AT specific, but whit is working to make it be more general, and factor out the re-usable bits. I'm sure he can chime in. i can add a bit more to this. wicked isn't really a full wiki implementation, instead it focuses on the one feature that, IMO, is what really defines a wiki: the ability to very easily link to existing content, or create new content if the existing content doesn't already exist. notable wiki features that wicked does NOT cover include the handling of any particular formatting markup (wicked doesn't care), and revision control. wicked was developed against AT, in that specific AT fields on specific content types can be made wicked-aware, so that they support wicked's ((wiki syntax)). thus it becomes very easy to add wiki-like behaviour to any existing content type. we don't want this to be tightly coupled, however, and some effort has been made to decouple it. ideally, the injection of the wicked evaluation, the wiki syntax (linking only, formatting concerns are outside wicked's domain) that wicked honors, and the means for performing the wiki evaluation (currently makes heavy use of CMF's portal_catalog for this) would all be pluggable, usable in any arbitrary python environment that supports adaptation. considerable progress has been made on this front, but i'm not sure what the absolute latest is. if anyone wants to see wicked in action, you can play around in the sandbox project on openplans.org: http://openplans.org/projects/sandbox. the code is available in the plone collective: http://dev.plone.org/collective/browser/wicked. hth, -r ___ 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-checkins] SVN: Zope3/trunk/src/zope/publisher/http.py Fix the level 2 test failure in zope.app.twisted.tests.test_inputbuffering.
Hi Marius, On Monday 09 October 2006 20:13, Marius Gedminas wrote: > Log message for revision 70591: > Fix the level 2 test failure in > zope.app.twisted.tests.test_inputbuffering. > I have looked into this a long time but since at the time the problem only appeared in a Python patch so I dropped the issue. I then looked into this 1 / 2 weeks ago and then I remembered how painful this was. The issue, or part of the issue, is that the WSGI specification says that: The optional "size" argument to readline() is not supported, as it may be complex for server authors to implement, and is not often used in practice. I have managed to patch cgi.FieldStorage up with a work around which I sent to the web-sig mailing list and which I have finally got around to creating a new bug report for python after seeing your checkin - see http://sourceforge.net/tracker/index.php?func=detail&aid=1573931&group_id=5470&atid=105470 The sole response on web-sig mailing list was to change the WSGI specification. But I wonder how many other WSGI applications are effected by this. If it just Zope and Twisted then changing the specification should be ok, otherwise things could get very messy for WSGI. Michael -- Michael Kerrin 55 Fitzwilliam Sq., Dublin 2. Tel: 087 688 3894 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.3 2.4 Linux remy
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Linux remy. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8080 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.3 2.4 Windows 2000 zc-bbwin
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Windows 2000 zc-bbwin. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8080 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver BUILD FAILED: failed failed slave lost sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Windows 2000 zc-bbwin3
The Buildbot has detected a failed build of Zope3 trunk 2.4 Windows 2000 zc-bbwin3. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8079 Blamelist: alga,dobe,jens,mgedmin BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.3 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8080 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8079 Blamelist: alga,dobe,jens,mgedmin BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8079 Blamelist: alga,dobe,jens,mgedmin BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.2 2.4 Windows 2000 zc-bbwin
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000 zc-bbwin. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8078 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver,yuppie BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.2 2.4 Linux remy
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Linux remy. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8078 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver,yuppie BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches 3.2 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 8078 Blamelist: alga,andreasjung,baijum,dobe,faassen,fdrake,flox,jens,jim,jukart,mgedmin,poster,schwendinger,shh,tseaver,yuppie BUILD FAILED: failed test sincerely, -The Buildbot ___ 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.testbrowser + unicode URL
Adam Groszer wrote: Happened to pass a unicode instead of str URL to browser.open(). That caused a nasty exception in Cookie.py. Might be worth an assert()? I don't think so, but it's really more of a question for the mechanize list: [EMAIL PROTECTED] -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] zope.testbrowser + unicode URL
Hello, Happened to pass a unicode instead of str URL to browser.open(). That caused a nasty exception in Cookie.py. Might be worth an assert()? -- Best regards, Adam -- Quote of the day: Look and you will find it-what is unsought will go undetected. - Sophocles ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Handling of empty prefixes in zope.formlib and zope.app.form
On Thu, Sep 28, 2006 at 11:34:30PM +0200, Jacob Holm wrote: > Would it be OK to change the handling of empty prefixes in zope.formlib > and zope.app.form to *not* add that leading period in case of an empty > prefix? The current behavior is undocumented and could be considered a > bug (if not in the code then in the documentation and tests). Since no one else commented, I guess I could do it. Personally, I think it's OK. As you pointed out, having an id with a leading period is not valid XHTML, so I'd be surprised if anyone would depend on it. It'd be good to have someone responsible for zope.formlib +1 the patch, but if no one gives it -1 one in the near future, it should be OK to merge it anyway. > I have attached a small patch against the current trunk that does what I > want. All current tests pass, but no tests for the new behavior has been > added (yet). It's a good sign that no existing tests failed, but you should of course add tests for this functionality before merging. > The patch is minimal in the sense that no API is changed, > only the behavior related to empty prefix strings. Specifically it does > not change the constructor of the (internal?) class > zope.formlib.form.Widgets to take the actual prefix instead of just its > length. Doing this would simplify the code and allow some sanity checks, > but could cause breakage if the class is used anywhere else. I think it's good to do it the way you did it. I have an example where I use the Widgets class directly, so changing its API would be harder, since you'd need to ensure backwards-compatibility. > Comments? The patch looks non-intrusive, i.e, as you said no API is changed, so it shouldn't break anyone's code. I have a few minor comments on the code itself. > Index: src/zope/formlib/form.py > === > --- src/zope/formlib/form.py (revision 70426) > +++ src/zope/formlib/form.py (working copy) > @@ -208,6 +208,14 @@ > return zope.security.canAccess(context, writer.__name__) > return zope.security.canWrite(context, field.__name__) > > +def prefixjoin(*args): > +return '.'.join(filter(None,args)) I rarely see filter being used these days. Personally I prefer list comprehensions instead. return '.'.join([argument for argument in args if argument]) If you use filter there should at least be a space after the comma. return '.'.join(filter(None, args)) Although personally I wouldn't have bothered creating 'prefixjoin' at all. The code it replaced was so simple, so I wouldn't say it's more readable to have it factored it out into a function, and it would have made the patch even smaller :) Also, the name of the function isn't that clear. Sometimes it's used to join two prefixes, sometimes it's used to join a prefix and a field name. > + > +def prefixlen(prefix): > +if not prefix: > +return 0 > +return len(prefix)+1 > + > def setUpWidgets(form_fields, Normally I would comment on the PEP-8 correctness, and say that the top-level functions should be separated by two blank lines. I see that you are consistent with the rest of the file, though, so I won't comment on it. It wouldn't hurt being a bit inconsistent and add docstrings to the added functions, though. Understanding the implementation of zope.formlib can be quite hard at the moment, since there are practically no docstrings at all. This is an excellent example where a docstring is needed, since it's not easy to know whether the period should be considered part of the prefix or not. Regards, Bjorn ___ 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: IMPORTANT: How to look up adapters
Tres Seaver wrote: Jim Fulton wrote: ... There is one case where calling an interface isn't equivalent to get/queryAdapter. If you want to supply a context argument to specify a different place to look up adapters, you can't pass it to the interface. This is an extreme edge case. I know of no place in the Zope 3 tree where this is needed, but it is something we want to allow. I propose to provide new functions: getSpecialAdapter and querySpecialAdapter. These functions will require a context to be specified and will return the object if it provides the requested interface and will use __conform__ if it conforms to the interface. How about 'getAdapterInContext' and 'queryAdapterInContext', instead? OK. That's better, Thanks. The change is checked in BTW. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://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] Re: AW: Where should we place 3rd party packages?
I'm having trouble keeping up with this thread, so I'll just make some suggestions, which you can take as edicts if you want to. :) wrt the repository, if you choose to use the zope subversion repository: - Projects that want their own trunk, branches and tags or that have depenencies on external software not included in a standard zope+python installation should be placed in top-level project directories. - Otherwise, projects can put their packages in src. wrt installation Zope installations will have a software area and an instance area. Each will have lib/python directories. Software can be installed in these directories or anywhere else on the Python path. You will have full control over the Python path used via zope.conf. Zope 3 dosn't provide any packages that it expects things to be installed in. I hope this helps. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://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
[Zope3-dev] Undelivered Mail Returned to Sender
This is the Postfix program at host mail.zope.org. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program <[EMAIL PROTECTED]>: lost connection with mx-ha01.web.de[217.72.192.149] while sending HELO Reporting-MTA: dns; mail.zope.org Arrival-Date: Wed, 30 Jun 2004 12:25:02 -0400 (EDT) Final-Recipient: rfc822; florian.konnertz@web.de Action: failed Status: 4.0.0 Diagnostic-Code: X-Postfix; lost connection with mx-ha01.web.de[217.72.192.149] while sending HELO --- Begin Message --- ??changed: - - Dominik Huber -- forwarded from http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/IsarSprint --- End Message --- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Grrr. zope.org wikis are evil.
"Fred Drake" <[EMAIL PROTECTED]> on Montag, 9. Oktober 2006 at 5:20 Uhr +0100 wrote: >Didn't someone write one like this for Z3? Possibly as part of a >zope3.org thing? I now vaguely recall something being done, but >that's about all I remember. > Hi, yes, we started such a thing at the NeckarSprint last year. Unfortunately it never got ready to use . It uses Kupu and TinyMCE as WYSIWYG editors besides ReST: http://svn.zope.org/zope3org/trunk/src/zorg/wikification/ I fear that I will not be able to continue this work in the next few months, since I have to concentrate on my Bebop project. In this project we try to implement a lot of additional features like previews, versioning, diff views, integration with blog and news views, filesystem synchronization etc.I would love to see Bebop as a basis for a zope3.org site, but that's not realistic at the moment. For the zope3.org site it would probably the best to use an existing tool like Trac which is dedicated to the need of programmers. 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