Well, tried troubleshooting this a bit more. I have this little snippet in my kid template:
<?python select_folders = [f for f in folders if (f.id>0 and f.id!=current_folder.id)] ?> <option py:for="f in select_folders" value="$f.id" >$f.name</option> This is what is causing the exception. What is odd is that if I replace the $f.name in the <option> with $f.id, there is no exception. I am passing the template current_folder and folders (which is a list of folder objects I have defined in model).
