>>> m.connect('gallery_thumb',
'images/gallery/:(image_id)_:(image_size).jpg', image_size='thumbnail')
>>> m.connect('gallery', 'images/gallery/:(image_id).jpg')
Well, that's generally the same trick as discussed earlier as a
workaround - forcing parameter difference (here - extra param). I do
not understand why named routes works the way you describe. Does there
exist any case when one wants to specify the named route while calling
url_for and then have url generated by another route???
Thanks for the explanation, nevertheless, while I do not understand
why it is implemented as it is, I at least understand what is
happening.
If the logic is to stay, I would suggest adding some more docs about
it, it is really confusing for somebody new to Routes.
(in general, Routes Manual would probably benefit from separate
section about 'url_for', currently the manual is oriented more towards
routes resolution)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
