Re: [Repoze-dev] About location-aware object in Traversal

Hey Tim, You'll want to subscribe your gmail.com address to the list if you want these emails to make it to the list. Forwarding this one for you. - C Tim Hoffman wrote: > HI George > > Glad you found it, I didn't know if what I was saying was particularly > of interest so didn't bother with

[Repoze-dev] [issue108] repoze.what decoratos should be usable in python2.5 too

New submission from Marcin : http://pypi.python.org/pypi/decorator this package allows to use decorators in python 2.5 same way as we could in 2.6, i think its quite important because just recently i had the unpleasant situation of having to run on python 2.5 software developed on 2.6, it was a p

Re: [Repoze-dev] About location-aware object in Traversal

Resending this because it was discarded by Mailman (sent from an unsubscribed address, apparently). - C Tim Hoffman wrote: > HI George > > You can really have a number of ways of supporting traversal and > __name__, __parent__ > > I am running repoze.bfg on app engine to implement a simple cms

Re: [Repoze-dev] About location-aware object in Traversal

george hu wrote: > As BFG document stated, all the object instances of model graph in > Traversal must have __name__ and __parent__ attribute, and they should > be hierarchically "linked". As the traversal wiki example reveals, page > objects are implementing this rule. But when I look at the so

[Repoze-dev] About location-aware object in Traversal

As BFG document stated, all the object instances of model graph in Traversal must have __name__ and __parent__ attribute, and they should be hierarchically "linked". As the traversal wiki example reveals, page objects are implementing this rule. But when I look at the source code of bfgsite, I can'

[Repoze-dev] Beware: import side-effects

Be careful when using "legacy" Zope packages; if you import them before the BFG thread-local patch, they might register components with the global base components registry instead of your app's registry (because the ``getGlobalSiteManager`` object is imported and used for registration). \malthe __

[Repoze-dev] [issue103] repoze.bitblt removes doctype

Brian Sutherland added the comment: You're right on the slowness of beautifulsoup compared to lxml: http://blog.ianbicking.org/2008/03/30/python-html-parser-performance/ __ Repoze Bugs __ ___

[Repoze-dev] [issue103] repoze.bitblt removes doctype

Malthe Borch added the comment: Speed matters; ``lxml`` is very fast and does not incur any significant overhead. I feel that BeautifulSoup would (this might not be correct). Regular expressions are very fast, and sometimes brittle. Everything's a compromise. However, image-tags are usually

[Repoze-dev] [issue103] repoze.bitblt removes doctype

Brian Sutherland added the comment: As an alternative to regexes, there's always BeautifulSoup http://www.crummy.com/software/BeautifulSoup/documentation.html -- nosy: +jinty __ Repoze Bugs

[Repoze-dev] [issue103] repoze.bitblt removes doctype

Brian Sutherland added the comment: I also was bitten by this. Attached is the patch I am using, it includes and expands on the originally posted patches using dbaty's "more complex than it should be" method to keep the doctype out of html that didn't already have it. Using regexes does sta