Skip to main content

Recursion Bites with Complex Nevow Pages

There is a recently discovered issue with Nevow's Athena LivePages. LiveFragment nesting fails if the nesting gets too deep, due to repeated cloning of the contexts, including the full chain of parents back to the root of the document. This was hitting the call depth limits in some tests idnar was working on. I found this to be a little worrysome, as my designs for the current project included some relatively deep nesting of LiveFragments; at least, as deep as the tests that found the error. Eventually, contexts are to be removed from nevow entirely, as I understand it, but this is far down the road. A temporary solution was needed, besides just not using so much nesting. I decided that instead of redesigning the system I was building, I would fix the bug, and I have. I posted Trac Ticket #602 along with a patch that fixes it.

Recursion is a very useful software construct, but sometimes it can bite you in the end when you don't even expect it to. There is usually a way around it, but I do wish there was a more explicit way in some language to express a construct meant to avoid recursion. All I had to do was traverse up the parent attributes and create a list of all the parents, in order. I took each of these, and if the clone method was the same as our own, so we know for sure how it works, I just manually clone it and make it the parent of the clone of its original child. This way, no recursion is ever needed between parents being cloned, unless a different context class is being used, which also redefines the clone method. If that becomes a problem, it should be fixable as easily.

This may seem a little hackish, but its a common enough issue that I am really surprised there has never been a really good recursion alternative in any language. I'm not sure what form this would take, but in places it would be nice to say "this works like recursion, but without recursing".

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho