#1987: [PATCH] Bug in controllers.py _find_object() function causes problems 
for a
controller's lookup() method in TG2.0
------------------------+---------------------------------------------------
 Reporter:  alevinsn    |        Owner:  anonymous
     Type:  defect      |       Status:  new      
 Priority:  normal      |    Milestone:  1.9.7a5  
Component:  TurboGears  |      Version:  trunk    
 Severity:  normal      |   Resolution:           
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by TimurIzhbulatov):

  * summary:  Bug in controllers.py _find_object() function causes problems
              for a controller's lookup() method in TG2.0 =>
              [PATCH] Bug in controllers.py _find_object()
              function causes problems for a controller's
              lookup() method in TG2.0

Comment:

 Well, it looks like inside `tg/controllers.py` the remainder variables are
 *supposed* to be lists — this comparison statement and the call of
 `reminder.pop()` in `_find_object` point to that. The root cause the bug
 is that the `*remainder` extended argument of a `lookup` method is
 normally unpacked to a tuple when the method is called.

 So, I think the fix should just make sure that the remainder returned from
 object's lookup method is converted to a list.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/1987#comment:1>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to