I recently noticed a difference in Nevow from some old SVN checkout vs 0.3. 0.3's behavior got in my way while writing a nevow app, but I'm not sure if it's considered a bug.
The minimal example is below. The difference is that in the old Nevow, it would display "Hi"; now it displays big-red-NONE.
After some debugging with the help of Tv and dreid on #twisted-web, we discovered that it was the change that added an IGettable to rend.Fragment. It __implements__ IGettable and implements 'get' as 'return self.original', which is None. Removing IGettable from __implements__ and deleting 'def get' makes it display "hi".
I'll probably work around this problem by not passing the Fragment through the data machinery, and instead look it up and return it directly in a render function. I'm just notifying you guys about this issue and you can decide whether or not it should be considered a bug. I'm interested in knowing why this IGettable implementation was added to Fragment, as well.
Thanks,
On Wed, 13 Oct 2004 16:10:42 +1100, Christopher Armstrong radeex@gmail.com wrote:
I'll probably work around this problem by not passing the Fragment through the data machinery, and instead look it up and return it directly in a render function.
This was harder than I expected, as I wanted to render a list of these Fragments with the 'sequence' renderer -- meaning I'd have to pass it as data to that renderer, which still showed the same problem.
What I did to work around it, then, was to define a subclass of Fragment which specified __implements__, leaving out IGettable.
participants (2)
-
Christopher Armstrong -
David Reid