Re: [Zope-dev] patterns for using sphinx with the Zope Toolkit?
Martijn Faassen wrote: I am interested in creating sphinx-driven documentation for Zope Toolkit packages. I'd like to maintain the documentation for a package (say, zope.component) in that package, in a 'doc' directory. I have a couple of packages that make good use of the my current pattern-that-I'm-aiming-for-with-all-my-packages: http://packages.python.org/testfixtures/ http://packages.python.org/checker/ I aim to support the build and release process in the docs, specifically building the docs and checking the ReST to go to PyPI: http://packages.python.org/checker/development.html#building-the-documentation I do this with the following buildout, the docs section is largely boilerplate that I copy from project to project changing only the one egg name: https://secure.simplistix.co.uk/svn/Simplistix/checker/trunk/buildout.cfg I use Manuel for testing, wired in firstly to the package's setup.py: https://secure.simplistix.co.uk/svn/Simplistix/checker/trunk/setup.py ...and then I always have a file for testing the docs: https://secure.simplistix.co.uk/svn/Simplistix/testfixtures/trunk/testfixtures/tests/test_docs.py https://secure.simplistix.co.uk/svn/Simplistix/checker/trunk/checker/tests/test_docs.py I routinely do development on Windows, Mac and Linux and all of the above work on all of them. hth, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] patterns for using sphinx with the Zope Toolkit?
On Tue, Jan 12, 2010 at 12:35 PM, Chris Withers ch...@simplistix.co.uk wrote: Martijn Faassen wrote: I am interested in creating sphinx-driven documentation for Zope Toolkit packages. I'd like to maintain the documentation for a package (say, zope.component) in that package, in a 'doc' directory. I have a couple of packages that make good use of the my current pattern-that-I'm-aiming-for-with-all-my-packages: http://packages.python.org/testfixtures/ http://packages.python.org/checker/ I would support adding documentation to packages.python.org It's very easy as Chris show. I am also using a similar pattern for BlueBream. This is how I am uploading documentation for BlueBream: ./bin/sphinxbuilder;./bin/buildout setup . upload_sphinx You can see the Buildout here: http://svn.zope.org/bluebream/trunk/ In setup.cfg, we can mention the upload-dir option like this: [upload_sphinx] upload-dir = docs/output/html BTW, to upload docs, no need to make a new release. Anyone who is having ownership can upload docs. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Mon Jan 11 12:00:00 2010 UTC to Tue Jan 12 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 11 20:36:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013365.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 11 20:38:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013366.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:40:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013367.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:42:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013368.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:44:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013369.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:46:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013370.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Stepping back as Zope 2 release manager
Hi Andreas, I also want to join the list of people to thank you for your long-lasting and most valuable efforts. Having done a bunch of releases myself, I know that the title comes with lots of connotations as master bug fixer, fighter, etc. Thanks a lot for all you have done! Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.form: GroupForm and ModificationEvents
Hi, it seems to me that z3c.form.group.GroupForm does not send enough ModificationEvents: only one event for the context of the GroupForm but not for each modified object in the groups. In a project of mine I have the following situation: I have a folder with some contained objects. A GroupForm displays the schema fields of the folder and the ones of all contained objects. When I modify one of the fields of a contained object I would expect a ModifiedEvent for this object. (Is this a valid expectation?) But GroupForm sends only one ModifiedEvent for the Folder (context of the form). This is even wrong in my case. At least the ModifiedEvent-Subscriber in zope.dublincore can't handle this and wrongly marks only the folder as modified. Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? 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 https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form: GroupForm and ModificationEvents
Hi Michael Betreff: [Zope-dev] z3c.form: GroupForm and ModificationEvents Hi, it seems to me that z3c.form.group.GroupForm does not send enough ModificationEvents: only one event for the context of the GroupForm but not for each modified object in the groups. In a project of mine I have the following situation: I have a folder with some contained objects. A GroupForm displays the schema fields of the folder and the ones of all contained objects. When I modify one of the fields of a contained object I would expect a ModifiedEvent for this object. (Is this a valid expectation?) But GroupForm sends only one ModifiedEvent for the Folder (context of the form). This is even wrong in my case. At least the ModifiedEvent-Subscriber in zope.dublincore can't handle this and wrongly marks only the folder as modified. Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? I'm not using group forms so I can't say if it's wrong or right. But I have a question. Does the ISublocation adapter not dispatch the modified event to the containers items? Are you sure that you use the ISublocation adapter which will dispatch events to container items? If this will not help, I think it's not bad to implement such an event notification. Probably in a method or with a marker which allows others to simply disable the additional event notification. Regards Roger Ineichen 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 https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Preparing a new release for zope.sendmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabio Tranchitella wrote: Hello, I'm preparing a new major releases for zope.sendmail, merging the improvements and new features from the repoze.sendmail package. Here there is a copy of the changelog: - Removed dependency on ``zope.security``: the security support is optional, and only available if the ``zope.security`` package is available. This change is similar to the optional security support introduced in ``zope.component`` 3.8.0, and in fact it uses the same helpers. - Sort by modification time the messages in zope.sendmail.maildir so earlier messages are sent before later messages during queue processing. - Added the new parameter ``processorThread`` to the queuedDelivery ZCML directive: if False, the QueueProcessorThread is not started and thus an independent process must process the queue; it defaults to True for b/c. - Provide a console script ``zope-sendmail`` which can be used to process the delivery queue in case processorThread is False. The console script can either process the messages in the queue once, or run in daemon mode. The changes are quite intrusive, but fully backwards compatible. If nobody objects, i will make the new release on Sunday, the 10th. The 3.7.0 version breaks Zope 2.12, which still expects to be able to import QueueProcessorThread from the old location. I worked around the problem for the moment by pinning 'zope.sendmail3.7.0', but it seems to me that the BBB import should be kept (likely forever). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktNFqcACgkQ+gerLs4ltQ68AACgrlKR2VXg/2fQB0vgK7LRPxaC ux4AnjgK4YnZ5RMKksgfx2d2CYP8mVne =caS/ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] New Zope2 releases available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In order to address a potential cross-site scripting problem in Zope's fallback error message, we are releasing new versions of the 2.8, 2.9, 2.10, 2.11, and 2.12 release lines. The issue, reported by the Plone team, could be triggered by a combination of a broken 'standard_error_message' template, plus an error whose 'str' contained markup. Although the 2.8, 2.9, and 2.10 branches are formally out-of- maintenance, they are still in very wide use. the Zope security response team decided to release versions for those branches, in addition to the 2.11 and 2.12 branches which are still being supported under normal policy. Releases are available here: - - Zope 2.8.12, http://www.zope.org/Products/Zope/2.8.12 - - Zope 2.9.12, http://www.zope.org/Products/Zope/2.9.12 - - Zope 2.10.11, http://www.zope.org/Products/Zope/2.10.22 - - Zope 2.11.6, http://www.zope.org/Products/Zope/2.11.6 - - Zope 2.12.3, http://pypi.zope.org/pypi/Zope2/2.12.3 Please note that the 2.12 releases are made only on the Python Package Index server, aka PyPI or the Cheeseshop. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktNPJYACgkQ+gerLs4ltQ6P1QCeJk6B+kIz9tXmN2oGYxFh1HuT WTIAoKevoMU9XOLmTJgpiRuLk7dHZnZv =PrpY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form: GroupForm and ModificationEvents
Michael Howitz wrote: Hi, it seems to me that z3c.form.group.GroupForm does not send enough ModificationEvents: only one event for the context of the GroupForm but not for each modified object in the groups. -1 to this being default behaviour. IObjectModifiedEvent is fired from EditForms, not from forms in general. Normally, an EditForm is used to edit a context. The groups could come from various locations (we use groups to create fieldsets based on schema hints, but they're all logically part of the same content object). I would not expect more than one event sent (in fact, doing this would significantly break code in the wild). In a project of mine I have the following situation: I have a folder with some contained objects. A GroupForm displays the schema fields of the folder and the ones of all contained objects. When I modify one of the fields of a contained object I would expect a ModifiedEvent for this object. (Is this a valid expectation?) But GroupForm sends only one ModifiedEvent for the Folder (context of the form). This is even wrong in my case. At least the ModifiedEvent-Subscriber in zope.dublincore can't handle this and wrongly marks only the folder as modified. Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? I think you should override the action handler and do this for your project. I don't think it should be the default behaviour. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Stepping back as Zope 2 release manager
Great job Andreas, thanks a lot. Best, -Simon ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
