Re: [Zope-dev] Mailinglist for Zope 2 bugs!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 16, 2009, at 23:01 , Wichert Akkerman wrote: Previously Sidnei da Silva wrote: Now for another question: how do people feel about moving Zope 3 and CMF bugs to a similar setup. That is, bug mail goes to a separate mailing list instead of directly to everyone that's a member of the teams in Launchpad. -0 I am happy with how CMF bugs are handled right now, so no reason to change a working system. Same here. There is no reason for yet another mailing list. I see it as needlessly duplicating what Launchpad already does. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkoPq5YACgkQRAx5nvEhZLJAcQCdG96B0QBfTP0sejW0Fsvm9gUq siwAniSY/78HbCY+TexHiqI8dFTeZAGc =1qcy -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 )
Re: [Zope-dev] Mailinglist for Zope 2 bugs!?
On 16.05.09 22:33, Sidnei da Silva wrote: On Sat, May 16, 2009 at 5:24 PM, filtered zopyxfil...@googlemail.com wrote: You were assimilated by Canonical? I don't understand the question. I'm just asking if it makes sense to have the same setup for CMF and Zope 3 as it is now for Zope 2 The downside of using a mailing list is possibly spam. The zope2-tracker must be open for postings from unsubscribed users since new Zope 2 bugreports must not necessarily come from members of the Zope 2 dev team but from any valid LP account. Andreas 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 )
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Sat May 16 12:00:00 2009 UTC to Sun May 17 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 20:52:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011723.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 20:54:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011724.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 20:56:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011725.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat May 16 20:58:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011726.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat May 16 21:00:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011727.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 21:02:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011728.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat May 16 21:04:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011729.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat May 16 21:06:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011730.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] z3c.form: Problem validating file uploads
Am 22.04.2009 um 14:48 schrieb Jacob Holm: Michael Howitz wrote: [...] Anyone having an idea for a possibly working solution? As I got no responsed, I'd like to put this issue into z3c.form's bugtracker. But which is the correct one? https://bugs.launchpad.net/zope3/ ? I don't know about the right tracker for this, but I think the right solution is 2) except that when widget.ignoreContext is True the default value should be looked up and validated instead. In other words, change z3c.form.validator.SimpleFieldValidator.validate to something like this (untested): [snipped really good suggestion] Unless I am missing something, the above code should compute the same value as z3c.form.widget.Widget.update would when ignoreRequest is True. Thus effectively converting NOT_CHANGED into the existing value before validating, Many thanks, Jacob. Your suggestion works very well. I implemented it on my branch and merged it to the trunk. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · 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] z3c.form 2.0 release?
Hi, what is still to be done for the z3c.form 2.0 release? Something I can help? Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · 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 )
Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
On 5/15/09 7:33 AM, Martijn Faassen wrote: Hanno Schlichting wrote: Chris McDonough wrote: I've created two codependent branches of zope.container and zope.lifecyclevent: [...] I don't know if merging this stuff is reasonable. I do understand the difference between lifecycle events and container events and the events I moved out are definitely container events. I just wonder if it matters to be completely correct terminology-wise here. The other alternative is to create another package. +1 on merging. I found it rather annoying so far to look for these interfaces in different places. To me it belongs to the lifecycle of an object to be part of a container. +1 too. Even though formally it might indeed be that these events are only container related, I did have the same frustration Hanno describes - these are very common events and often you want to subscribe to them and IObjectModified which is already in zope.lifecyclevents. These branches were merged. I made a new release of zope.lifecycleevent (3.5.2) to PyPI. zope.container does not have a new release yet. I may try to move IContained out of it (to zope.location) then make a new release. - C ___ 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] movedaddedremoved branches of zope.container and zope.lifecycleevent
Chris McDonough wrote: These branches were merged. I made a new release of zope.lifecycleevent (3.5.2) to PyPI. Thanks very much for doing this work. As a reminder for the future, please do release changes in the API (as in zope.lifecycleevent) as major releases (i.e. 3.6). I realize this requires an extra consideration when releasing that people seem to forget to do, so I've just adjusted the release instructions to make a note of this: (might not have shown up on the web yet, but will soon, step 2) http://docs.zope.org/zopetoolkit/process/releasing-software.html Regards, Martijn ___ 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] zope.* package dependencies report
In SVN, as a result of changes to zope.container, zope.lifecycleevent, zope.location, and zope.intid: zope.intid/trunk/ OK (20 dependencies) (delta -14 dependencies) zope.container/trunk/ OK (30 dependencies) (delta -2 dependencies) zope.location/trunk/ OK (08 dependencies) (delta -0 dependencies) zope.lifecycleevent/trunk/ OK (04 dependencies) (delta -0 dependencies) zope.formlib/trunk/ OK (61 dependencies) (delta -1 dependencies) zope.catalog/trunk/ OK (35 dependencies) (delta -1 dependencies) If you find any other thing depending on IObject*Event or Object*Event from zope.container you might be able to shed some dependencies by importing from zope.lifecycleevent instead. If you find any other thing depending on IContained from zope.contained, you might be able to shed some dependencies by importing from zope.location instead. - C On 5/14/09 11:16 PM, Chris McDonough wrote: FWIW, this may not be useful to some, but here's a (not-very-detailed) report on all the zope.* packages in Zope's SVN and the number of transitive dependencies they have. They are sorted in the order of most-dependencies-to-fewest. zope.introspectorui/trunk/ OK (96 dependencies) zope.paste/trunk/ OK (73 dependencies) zope.locking/trunk/ OK (72 dependencies) zope.html/trunk/ OK (71 dependencies) zope.psycopgda/trunk/ OK (65 dependencies) zope.testrecorder/trunk/ OK (63 dependencies) zope.formlib/trunk/ OK (62 dependencies) zope.catalog/trunk/ OK (36 dependencies) zope.principalannotation/trunk/ OK (35 dependencies) zope.rdb/trunk/ OK (34 dependencies) zope.intid/trunk/ OK (34 dependencies) zope.fssync/trunk/ OK (34 dependencies) zope.file/trunk/ OK (34 dependencies) zope.site/trunk/ OK (33 dependencies) zope.error/trunk/ OK (33 dependencies) zope.copypastemove/trunk/ OK (33 dependencies) zope.filerepresentation/trunk/ OK (32 dependencies) zope.container/trunk/ OK (32 dependencies) zope.viewlet/trunk/ OK (30 dependencies) zope.session/trunk/ OK (24 dependencies) zope.securitypolicy/trunk/ OK (21 dependencies) zope.introspector/trunk/ OK (20 dependencies) zope.contentprovider/trunk/ OK (20 dependencies) zope.traversing/trunk/ OK (18 dependencies) zope.server/trunk/ OK (18 dependencies) zope.bobo/trunk/ OK (18 dependencies) zope.publisher/trunk/ OK (17 dependencies) zope.principalregistry/trunk/ OK (15 dependencies) zope.sendmail/trunk/ OK (13 dependencies) zope.keyreference/trunk/ OK (13 dependencies) zope.authentication/trunk/ OK (13 dependencies) zope.wfmc/trunk/ OK (12 dependencies) zope.release/trunk/ OK (12 dependencies) zope.security/trunk/ OK (11 dependencies) zope.dublincore/trunk/ OK (11 dependencies) zope.pypisupport/trunk/ OK (10 dependencies) zope.minmax/trunk/ OK (10 dependencies) zope.kgs/trunk/ OK (10 dependencies) zope.index/trunk/ OK (10 dependencies) zope.bforest/trunk/ OK (10 dependencies) zope.annotation/trunk/ OK (09 dependencies) zope.testbrowser/trunk/ OK (08 dependencies) zope.location/trunk/ OK (08 dependencies) zope.mimetype/trunk/ OK (07 dependencies) zope.i18n/trunk/ OK (07 dependencies) zope.modulealias/trunk/ OK (06 dependencies) zope.pagetemplate/trunk/ OK (05 dependencies) zope.configuration/trunk/ OK (05 dependencies) zope.tales/trunk/ OK (04 dependencies) zope.sqlalchemy/trunk/ OK (04 dependencies) zope.schema/trunk/ OK (04 dependencies) zope.lifecycleevent/trunk/ OK (04 dependencies) zope.httpformdate/trunk/ OK (04 dependencies) zope.tal/trunk/ OK (03 dependencies) zope.size/trunk/ OK (03 dependencies) zope.deferredimport/trunk/ OK (03 dependencies) zope.component/trunk/ OK (03 dependencies) zope.testing/trunk/ OK (02 dependencies) zope.proxy/trunk/ OK (02 dependencies) zope.processlifetime/trunk/ OK (02 dependencies) zope.password/trunk/ OK (02 dependencies) zope.httpform/trunk/ OK (02 dependencies) zope.exceptions/trunk/ OK (02 dependencies) zope.documenttemplate/trunk/ OK (02 dependencies) zope.copy/trunk/ OK (02 dependencies) zope.browser/trunk/ OK (02 dependencies) zope.broken/trunk/ OK (02 dependencies) zope.z2release/trunk/ OK (01 dependencies) zope.xmlpickle/trunk/ OK (01 dependencies) zope.thread/trunk/ OK (01 dependencies) zope.structuredtext/trunk/ OK (01 dependencies) zope.sequencesort/trunk/ OK (01 dependencies) zope.interface/trunk/ OK (01 dependencies) zope.i18nmessageid/trunk/ OK (01 dependencies) zope.hookable/trunk/ OK (01 dependencies) zope.globalrequest/trunk/ OK (01 dependencies) zope.fixers/trunk/ OK (01 dependencies) zope.event/trunk/ OK (01 dependencies) zope.dottedname/trunk/ OK (01 dependencies) zope.deprecation/trunk/ OK (01 dependencies) zope.dependencytool/trunk/ OK (01 dependencies) zope.decorator/trunk/ OK (01 dependencies) zope.datetime/trunk/ OK (01 dependencies) zope.contenttype/trunk/ OK (01 dependencies) zope.cachedescriptors/trunk/ OK (01 dependencies) zope.weakset/trunk/
Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
I don't currently have access to publish zope.intid, but I think it's probably ready for a release too, BTW. - C On 5/17/09 1:34 PM, Martijn Faassen wrote: Chris McDonough wrote: These branches were merged. I made a new release of zope.lifecycleevent (3.5.2) to PyPI. Thanks very much for doing this work. As a reminder for the future, please do release changes in the API (as in zope.lifecycleevent) as major releases (i.e. 3.6). I realize this requires an extra consideration when releasing that people seem to forget to do, so I've just adjusted the release instructions to make a note of this: (might not have shown up on the web yet, but will soon, step 2) http://docs.zope.org/zopetoolkit/process/releasing-software.html Regards, Martijn ___ 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 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] Mailinglist for Zope 2 bugs!?
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org wrote: Same here. There is no reason for yet another mailing list. I see it as needlessly duplicating what Launchpad already does. So should we backtrack and undo the change to the zope-dev team which made it send messages to the publicly-open zope2-tracker mailing list? -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com ___ 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] Mailinglist for Zope 2 bugs!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 17, 2009, at 22:53 , Sidnei da Silva wrote: On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org wrote: Same here. There is no reason for yet another mailing list. I see it as needlessly duplicating what Launchpad already does. So should we backtrack and undo the change to the zope-dev team which made it send messages to the publicly-open zope2-tracker mailing list? You asked about the CMF bug tracker, and that's what I was referring to. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkoQiXgACgkQRAx5nvEhZLIHJQCeI0v51SLpjzi82IQn6+Akq3RC UEIAn1WaUcDiioLn9S1FtByyUzK3rEvM =eP/4 -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 )
Re: [Zope-dev] zope.app.publication dependencies (volunteers needed!)
On 5/15/09 7:00 AM, Martijn Faassen wrote: Hey, Chris McDonough wrote: I did a bit of research on the direct zope.app.* dependencies of zope.formlib. Cool! - I looked into its dependency on zope.app.form. It essentially uses a bunch of interfaces from the zope.app.form.interfaces package. I don't know whether it would be reasonable to move all those interfaces to zope.browser or somewhere else, but essentially moving those interfaces to somewhere neutral would break this particular dependency. I think it might make sense to reverse these dependencies - i.e. zope.app.form uses interfaces from zope.formlib for implementing its widgets. The old ZCML-based form mechanism in zope.app.form is moribund anyway so we can just ignore that. Don't know whether this would help the dependency structures though. I tried to go after this today (reversing the dependency setup between zope.formlib and zope.app.form). There are hundreds of changes that need to be made to move interfaces to zope.formlib. I made them (more or less mechanically) but then couldn't get the tests to pass. Since I don't actually use zope.formlib, I don't think it's appropriate that I commit anything. OTOH, I'm pretty convinced that this action would be a win for packages that depend on formlib. I found these: ./zope.app.component-3.7.0-py2.5.egg/EGG-INFO/requires.txt:zope.formlib ./zope.app.exception-3.5.0-py2.5.egg/EGG-INFO/requires.txt:zope.formlib ./zope.app.zcmlfiles-3.5.3-py2.5.egg/EGG-INFO/requires.txt:zope.formlib Are we done yet? ;-) - C ___ 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 )
