- Zope - Zope lists

Stripping Quotes
by Tom Von Lahndorff 29 Aug '07

29 Aug '07

Whats the best way to strip (double and/or single) quotes from a string in python and/or dtml? Thanks.

2 1

Deploying with buildout (was: buildout, instancemanager, and eggs)
by Ross Patterson 28 Aug '07

28 Aug '07

We have a Plone 3.0/Zope 2.10 application that we need to develop on, maintain and deploy to a ZEO server and multiple ZEO clients. Currently we use svn bundles of Zope and Plone and our own packages and products in one big svn:externals definition. We also use some more recent versions of certain products and packages than those included in the upstream svn:externals. For example: Zope svn://svn.zope.org/repos/main/Zope/branches/2.10 Zope/lib/python/zope/app/interface svn://svn.zope.org/repos/main/zope.app.interface/trunk/src/zope/app/interfa… Though I haven't seen any documentation to this effect, svn seems to treat the second svn:externals as a "svn switch" on "svn up". So one question I have is how would I "override" the versions of some package like this using buildout? Another question I have is that there aren't releases for all the dependencies our application has. I'm wondering what the best way is to define a canonical release for deployment to our cluster. Ideally, we'd have a buildout (or whatever) on a staging server where we're testing the candidate for deployment and then when all tests pass that *exact* source should be deployed to the cluster. How might one do this without upstream releases? Is there a way to get buildout and setuptools to play together so that I can build a source distribution from the test passing buildout on staging? Is there a way I can have a buildout on each cluster node such that a simple ./bin/buildout will get the latest deployment release for that node? Ross

2 4

Can't start Zope
by Tom Von Lahndorff 28 Aug '07

28 Aug '07

Getting the following error. Thanks in advance. ]# ./zopectl start Traceback (most recent call last): File "/opt/zope/Zope-2.10.1_Software/lib/python/Zope2/Startup/ zopectl.py", line 322, in ? main() File "/opt/zope/Zope-2.10.1_Software/lib/python/Zope2/Startup/ zopectl.py", line 280, in main options.realize(args) File "/opt/zope/Zope-2.10.1_Software/lib/python/Zope2/Startup/ zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/opt/zope/Zope-2.10.1_Software/lib/python/zdaemon/ zdoptions.py", line 273, in realize self.load_schema() File "/opt/zope/Zope-2.10.1_Software/lib/python/zdaemon/ zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ loader.py", line 65, in loadURL return self.loadResource(r) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/usr/local/lib/python2.4/xml/sax/__init__.py", line 33, in parse parser.parse(source) File "/usr/local/lib/python2.4/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/local/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/local/lib/python2.4/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/usr/local/lib/python2.4/xml/sax/expatreader.py", line 300, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ datatypes.py", line 398, in get t = self.search(name) File "/opt/zope/Zope-2.10.1_Software/lib/python/ZConfig/ datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/opt/zope/Zope-2.10.1_Software/lib/python/Zope2/Startup/ datatypes.py", line 21, in ? import OFS.Uninstalled File "/opt/zope/Zope-2.10.1_Software/lib/python/OFS/ Uninstalled.py", line 16, in ? import SimpleItem, Globals, Acquisition File "/opt/zope/Zope-2.10.1_Software/lib/python/OFS/ SimpleItem.py", line 26, in ? import AccessControl.Role, AccessControl.Owned, App.Common ImportError: No module named AccessControl.Role

3 3

Deleting a file in Python
by zozer＠cercy.net 28 Aug '07

28 Aug '07

I'm reading the zope book, 2.6. And I've worked through the ZopeZoo tutorial in chapter 11. I want to make it possible to delete entries in the GuestBook via its web interface. It uses a python script to create the file with the line: context.manage_addProduct['OFSP'].manage_addFile(id, title="", file=comments) I assume I could write something like: context.manage_deleteProduct['OFSP'].manage_removeFile(id) or maybe: context.manage_addProduct['OFSP'].manage_deleteFile(id) but I can't figure out where context.* is documented.

4 5

help with zodb server
by P. Nagaraj 28 Aug '07

28 Aug '07

Hi, I installed ZODB3-3.3.1. Problem is server says it starts, but is not there. I can understand what is happening. Please help! [root]# /usr/bin/zdctl.py -C /etc/zeoctl.conf start . . . . . . . . . . . daemon process started, pid=27100 [root]# /usr/bin/zdctl.py -C /etc/zeoctl.conf status daemon manager running; daemon process not running There is no activity in the log file Here is the info with "show" schemafile: '/usr/lib/python2.4/site-packages/zdaemon/schema.xml' configfile: '/etc/zeoctl.conf' interactive: None default_to_interactive: True zdrun: '/usr/bin/zdrun.py' python: '/usr/bin/python' program: ['/usr/bin/runzeo.py', '-C', '/etc/zeo.config'] backofflimit: 10 daemon: True forever: False sockname: '/soft/zeohome/zdsock' exitcodes: [0, 2] user: None umask: 022 directory: '/soft/zeohome' logfile: None hang_around: False Also, when I try another method, I get error [root@lnx7 tmp]# runzeo.py -a 127.0.0.1:9675 -f /soft/zeotmp/Data.fs Error: invalid value for -f '/soft/zeotmp/Data.fs': bad marshal data For help, use /usr/bin/runzeo.py -h Question: Who should own the directories and the Data.fs? Thank you very much! Regards, Nagaraj -- +----------------------------------+--------------------------------------+ Nagaraj Panyam | Office tel: +91-22-22782610 Dept of High Energy Physics | Office fax: +91-22-22804610 Tata Instt. of Fundamental Research| Home tel : +91-22-22804936 Mumbai - 400 005, INDIA | **Email** : pn(a)tifr.res.in +----------------------------------+--------------------------------------+

1 0

Help with DateTime.earliestTime()
by Eric Thomas 28 Aug '07

28 Aug '07

I've been having a site problem that I've tracked down to DateTime. Simply enough, the code snippets below both try to add 31 days to the first day in October. I'm expecting this to result in the first day of November. Good Example: >>> from DateTime import DateTime >>> start=DateTime('2005/10/01 01:00:00 GMT-5') >>> print start 2005/10/01 01:00:00 GMT-5 >>> earlyStart=start.earliestTime() >>> print earlyStart 2005/10/01 >>> print earlyStart+31 2005/11/01 Bad Example: (Here's the problem) >>> from DateTime import DateTime >>> start=DateTime('2005/10/01 01:00:00 US/Central') >>> print start 2005/10/01 01:00:00 US/Central >>> earlyStart=start.earliestTime() >>> print earlyStart 2005/10/01 >>> print earlyStart+31 2005/10/31 23:00:00 US/Central I've confirmed this occurs with several of the US/ timezones (US/Pacific, US/Alaska, etc) Can anyone help me figure out why the resulting date is coming up 1 hour short of the expected 2005/11/01 ? Thanks! Eric

7 11

MySql connector error
by Kevin 27 Aug '07

27 Aug '07

I have a mysqldb connector object based on http://svn.zope.org/mysqldbda/ under zope 2.9.7 Intermittently, I recieve an error *Shouldn't load state for 0xf5f137 when the connection is closed * I implemented this object because the standard mysql database adapter would fail if the connection was idle for some time with a similar kind of error. class MySQLdbAdapter(SimpleItem,ZopeDatabaseAdapter): ... def __call__(self): ... return connection there is an object stored, I call it and return the mysql cursor and use cursor to make queries ala the python module. Does this look famileir to anyone else, if so, how was the error overcome? -Kevin

2 2

How do I increment the number of entries in the Undo list?
by rieh25 25 Aug '07

25 Aug '07

I nedd to undo an action that appears in the second page, but apparently I need to undo all the later actions in order to make it work. Thanks. -- View this message in context: http://www.nabble.com/How-do-I-increment-the-number-of-entries-in-the-Undo-… Sent from the Zope - General mailing list archive at Nabble.com.

2 2

Global Variable In PT
by tonylabarbara＠aol.com 24 Aug '07

24 Aug '07

Hi: I have this code (editing out the extraneous) at the beginning of a page: <body bgcolor="#ffffff" tal:define="newRow string:yes"> After calling some other variables (specifically rotating through a changing ¨item¨ (for item in items...)), I try and change newRow: Then I try and call newRow: But it gives me the original value. Now, if I edit the page like this: it gives me a different value (the one I expect and want). Obviously, my ¨global¨ definition isn´t going global. What can I do to make it global; that is, call it outside of the span tag? TIA, Tony ________________________________________________________________________ Email and AIM finally together. You've gotta check out free AOL Mail! - http://mail.aol.com

3 2

New set of z3c.form* releases!
by Stephan Richter 24 Aug '07

24 Aug '07

Hi everyone, in the past month more project-related work, user feedback/requests and Javascript work has driven the development of the z3c.form framework. There are many new exciting features. There were also some small refactoring changes, which might require your CSS and tests to be adjusted. Please read the changes section below carefully! As always, the demos can be run using: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.4.0 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Thanks to Roger, Windows users should be able to run the demos this way now as well! Visually, not much has happened; there are no new demos. However, just wait until the next round of z3c.formjs* releases! Changes ------- - Feature: An event handler for ``ActionErrorOccurred`` events is registered to merge the action error into the form's error collectors, such as ``form.widgets.errors`` and ``form.widgets['name'].error`` (if applicable). It also sets the status of the form. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: Action can now raise ``ActionExecutionError`` exceptions that will be handled by the framework. These errors wrap the original error. If an error is specific to a widget, then the widget name is passed to a special ``WidgetActionExecutionError`` error. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: After an action handler has been executed, an action executed event is sent to the system. If the execution was successful, the event is ``ActionSuccessfull`` event is sent. If an action execution error was raised, the ``ActionErrorOccurred`` event is raised. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: The ``applyChanges()`` function now returns a dictionary of changes (grouped by interface) instead of a boolean. This allows us to generate a more detailed object-modified event. If no changes are applied, an empty dictionary is returned. The new behavior is compatible with the old one, so no changes to your code are required. (Thanks to Darryl Cousins for the request and implementation.) - Feature: A new ``InvalidErrorViewSnippet`` class provides an error view snippet for ``zope.interface.Invalid`` exceptions, which are frequently used for invariants. - Feature: When a widget is required, HTML-based widgets now declare a "required" class. - Feature: The validation data wrapper now knows about the context of the validation, which provides a hook for invariants to access the environment. - Feature: The BoolTerms term tokens are now cosntants and stay the same, even if the label has changed. The choice for the token is "true" and "false". By default it used to be "yes" and "no", so you probably have to change some unit tests. Functional tests are still okay, because you select by term title. - Feature: BoolTerms now expose the labels for the true and false values to the class. This makes it a matter of doing trivial sub-classing to change the labels for boolean terms. - Feature: Exposed several attributes of the widget manager to the form for convenience. The attributes are: mode, ignoreContext, ignoreRequest, ignoreReadonly. - Feature: Provide more user-friendly error messages for number formatting. - Refactoring: The widget specific class name was in camel-case. A converntion that later developed uses always dash-based naming of HTML/CSS related variables. So for example, the class name "textWidget" is now "text-widget". This change will most likely require some changes to your CSS declarations! - Documentation: The text of ``field.txt`` has been reviewed linguistically. - Documentation: While reviewing the ``form.txt`` with some people, several unclear and incomplete statements were discovered and fixed. - Bug (IE): In Internet Explorer, when a label for a radio input field is only placed around the text describing the choice, then only the text is surrounded by a dashed box. IE users reported this to be confusing, thus we now place the label around the text and the input element so that both are surrounded by the dashed border. In Firefox and KHTML (Safari) only the radio button is surrounded all the time. - Bug: When extracting and validating data in the widget manager, invariant errors were not converted to error view snippets. - Bug: When error view snippets were not widget-specific -- in other words, the ``widget`` attribute was ``None`` -- rendering the template would fail. Enjoy!

1 0