- Zope-Dev - Zope lists

Converters.field2date, allow empty string to return None?
by Brad Clements 02 Sep '00

02 Sep '00

One thing that has been bothering me is that I can't easily test my ZSQL Methods if they accept a date type unless I completely fill all the date arg types. For example, if the sqlmethod has argument type startdate:date='' and in the body I have <dtml-if startdate> ... When i use the test form, I can't leave the date field empty, otherwise I get a conversion error from Converters.field2date() I also have this problem with any form that has type date, if the end-user doesn't put a date in the form, I get a conversion error. Its okay with me to receive an empty string, which gets converted to None .. I just put NULL in the sql database. So .. what's the correct fix to allow empty fields to return either '' or None from field2date? I can alter Converters.py... I see that converters required: exists, but does that imply that all other converters allow an empty string to return None? Or do we need to add an explicit "optional" type? Either way, I'd like to fix this, but what's the best way? Brad Clements, bkc(a)murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements

2 1

ANN: XMLToObjects proposal
by Chris McDonough 02 Sep '00

02 Sep '00

I've created a proposal to gather feedback for implementing a facility to transform arbitrary XML directly into arbitrary Python objects. It's at http://dev.zope.org/Wikis/DevSite/Proposals/XMLToObjects. Please comment on the Wiki discussion page associated with it.

1 0

But I used __ac_permissions__! :S
by Chris Withers 01 Sep '00

01 Sep '00

Brian Lloyd wrote: > > Here's a quick thing to try- if 'subject' is an attribute > of your Article class, try adding: > > class Article(...): > subject__roles__=None > > then restart and see if you still get unauthorized... yup, I do :-( And besides, 'subject' is already in __ac_permissions__, as you can see: (a lot of stuff snipped out though ;-) __ac_permissions__ = ( ('View', ['subject','getThread'], ('Anonymous', 'Manager')), ) and I do appropriate Globals.default__class_init__'s... Man, I really have no idea, and not even any clue where to look. The big factor seems to be that 'subject' is a string. I had a similar problem with the SquishFile class with the 'icon' attribute. When it was a string: # protected by 'View' permission icon = 'misc_/Squishdot/squishfile_img' ...even though it was a class variable and protected in __ac_permissions__, I was getting very similar errors to the above... I was lucky, in that case, because it was a class variable, I could turn it into a method: # protected by 'View' permission def icon(self): return 'misc_/Squishdot/squishfile_img' ...and, lo and behold, no more security errors from there... :S Unfortunately, the string attributes in the Article class are instance attributes, not class attributes, so I can't do the same thing :-( Any ideas? cheers, Chris

2 1

RE: [Zope] ZCatalog and OR searching
by Casey Duncan 01 Sep '00

01 Sep '00

It would be wonderful if ZCatalog could support something like a SQL where clause for doing complex searching. Is this anything anybody has in the works or would be interested in working on? I forsee something like Catalog(query_expr="title contains 'foo' and not title contains 'bar' or title contains 'spam'"). Support for the simple searching in existence now should of course remain. Perhaps some code could be borrowed from Gadfly or something. I would be interested in working on something such as this, but I don't want to reinvent the wheel. Anyone with futher input or info, please let me know. -Casey Duncan ----- Original Message ----- Date: Fri, 01 Sep 2000 11:43:30 +0100 From: Chris Withers <chrisw(a)nipltd.com> Organization: New Information Paradigms To: Dieter Maurer <dieter(a)handshake.de> CC: Francois-Regis CHALAOUX <Francois-Regis.CHALAOUX(a)sanofi-synthelabo.com>, Receipt Notification Requested <zope(a)zope.org> Subject: [Zope] ZCatalog and OR searching Dieter Maurer wrote: > A ZCatalog search usually combines searches to the different > indexes with an "And". > You want to combine them with an "Or". Don't you wish there was a decent query language for ZCatalog so this kindof rediculous complexiting to achieve a simple outcome wasn't necessary? cheers, Chris PS: The example in the Advanced ZCatalog How-To does away with most of the catalog's advantages (like lazy searches, small results set, etc)

1 0

ZCatalog: text searches fail with sort_on + patch
by Steve Alexander 01 Sep '00

01 Sep '00

I'm getting an error in Catalog when I specify sort_on on a field-index, and also search on a text index. Zope 2.2.1, Python 1.5.2 Error Type: TypeError Error Value: loop over non-sequence Traceback (innermost last): File lib/python/ZPublisher/Publish.py, line 222, in publish_module File lib/python/ZPublisher/Publish.py, line 187, in publish File lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: ProviderContainer) File lib/python/ZPublisher/Publish.py, line 171, in publish File lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: search) File lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: search) File lib/python/OFS/DTMLDocument.py, line 177, in __call__ (Object: search) File lib/python/DocumentTemplate/DT_String.py, line 528, in __call__ (Object: search) File lib/python/DocumentTemplate/DT_In.py, line 630, in renderwob (Object: SiteIndex) File lib/python/Products/ZCatalog/ZCatalog.py, line 463, in searchResults (Object: Traversable) File lib/python/Products/ZCatalog/Catalog.py, line 602, in searchResults File lib/python/Products/ZCatalog/Catalog.py, line 555, in _indexedSearch TypeError: (see above) This seems to be a simple type incompatibility error. Attached is a patch that fixes this. In Collector, http://classic.zope.org:8080/Collector/1586/view -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net *** Catalog.py.orig --- Catalog.py *************** *** 552,558 **** if intset: append((k,LazyMap(self.__getitem__, intset))) else: ! for r in rs: append((sort_index._unindex[r], LazyMap(self.__getitem__,[r]))) --- 552,558 ---- if intset: append((k,LazyMap(self.__getitem__, intset))) else: ! for r,x in rs.items(): append((sort_index._unindex[r], LazyMap(self.__getitem__,[r])))

1 0

StructuredText.py - bug or feature
by nw_moriarty 01 Sep '00

01 Sep '00

I took an example of strucuture text from the document string of StructuredText.py - Text encloded by double quotes followed by a colon, a URL, and concluded by punctuation plus white space, *or* just white space, is treated as a hyper link. For example: "Zope":http://www.zope.org/ is ... Is interpreted as '<a href="http://www.zope.org/">Zope</a> is ....' Note: This works for relative as well as absolute URLs. The paragraph ends with a 'example' but the next line beging with "Zope" is not formatted as <PRE> but as a link. If one moves the 'For example:' in a new paragraph we have better results. Am I missing something? Nigel --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy.

1 0

_setObject error - urgent!
by Andy McKay 01 Sep '00

01 Sep '00

Hi, I think I have traced my error with cut and paste, I am getting an error on _setObject. If the object is not registered with Zope properly this will be a problem. Basic synopsis: Im importing an object from a script so Im getting a handle to the folder I would like the object to be in: this is obj. Then I call add and set object: obj._setObject(id, globals()[doctype](id, m)) This rather unusual syntax allows me to use a constructor for man different objects. The type is specified in 'doctype', I then get this error: 2000-08-31T16:56:57 PROBLEM(100) ASPNDoc Error: [exceptions.NameError: cat] Any ideas? Thanks in advance

1 1

RE: [Zope-dev] Re: Better encapsulation is good...
by Brian Lloyd 01 Sep '00

01 Sep '00

> > Did you run the Article class through > Globals.default__class_init__()? > > E.g. (at the module level), e.g.: > > > > Globals.default__class_init__(Article) > > > > Yes, I tried this too, (saw it in the mailing list archive). (I'm coming to this late, so ignore me if this is covered ground...) Are you certain that you are not losing the acquistion context on your Articles somehow? For example, if you are not doing a getattr on the container to get an article, you may need to maintain the acquistion chain yourself: class Article(Acquistion.Implicit): ... class Articles: """The container for articles. Note that I dont really contain them though - I get them from a database or something (or create them on the fly)""" def getArticle(self, id): # we create an Article on the fly, so we have to # "wrap" the object in the context of its container # to preserve the acquisition chain (and security # depends on an intact acquisition chain) item=Article(id) # this is the wrapping! return item.__of__(self) Hope this helps... Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

2 2

Re: [Zope-dev] Compatibility issues: ZPatterns 0.4.2,LoginManager 0.9.0
by Steve Alexander 01 Sep '00

01 Sep '00

Phillip Eby wrote: > > * We would like to drop support for Specialists directly containing data > plug-ins. This feature was intended to allow for acquiring shared data > plug-ins from within Racks, so that common attribute or sheet providers > could be shared among Racks without copying. In practice, Ty and I have > never once used this capability, and it could be easily replaced with the > ability to "include" a SkinScript within another SkinScript, if we take > advantage of 2.2.x-isms. I have been putting CatalogTriggers as DataManagers directly in Specialists. This seems to me the obvious place to do some triggering action that applies over all the Specialist's racks, but which has nothing to do with storage. I don't yet use SkinScript. However, I imagine there are a number of uses for Triggers that apply at the level of abstraction of a Specialist. Please think about keeping the feature, if it doesn't make things too complicated. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net

2 5

RE: [Zope-dev] Acquisiton, wrapping and persistence...
by Brian Lloyd 01 Sep '00

01 Sep '00

> > Are you certain that you are not losing the acquistion context > > on your Articles somehow? > > There's a good chance that's right :S > Is there anything bad about storing wrapped attributes in a persistent > object? > Butch seemed pretty religious about unwrapping objects before > he stored > them, and maybe he ain't quite wrapping them up right on the > way out... At one time (Jim would know if this is still the case), the ZODB didn't want to store wrapped objects. Wrapping (or "context") is a run-time, in-memory thing while "containment" is a persistent thing. Wrapping really shouldn't be persistent, since context changes based on the way you _access_ things and isn't really meaningful to the persistent state of an object hierarchy. When you access a subobject via getattr, the Acquisition machinery will ensure that the returned object is correctly wrapped. If you store objects under the hood in a way that does not go through getattr, you always need to ensure wrapping yourself: class Things(Implicit): # Things contains individual Thing objects. They are # stored as direct attributes. def getThing(self, id): # dont need to wrap, since we're going through getattr return getattr(self, id) class TrickyThings: # TrickyThings stores its Things internally in a dict # and thus we don't go through getattr. So we have to # do wrapping manually def __init__(self): self.things={} def getThing(self, id): # need to wrap object before returning it object=self.things[id] return object.__of__(self) ...so I'd be looking for some of this sort of trickiness in the code where the result is not being wrapped. > This may be a stupid question, but why does the object need to be > wrapped for security to work anyway? Because security is predicated on acquisition - that is why you can set a permission high in the tree and allow objects lower in the tree to "acquire permission settings" from that original setting. It lets you aggregate permission settings down the heirarchy. So - technically if _all_ of your permission settings were made directly on the object in question (i.e. all of the "acquire permission settings" checkboxes were unchecked and all appropriate permission settings were checked directly on that object), then it would work. But (as in most cases) you are using acquired settings then the object will have to be wrapped and have an intact acquisition chain at the time permissions are checked in order to get the result you expect. Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

1 0