I have a large Pylons app that I'm considering converting to Pyramid. My
main difficulty is the existing app uses Pylons routes like
/something/{name}{.format} extensively. I have considered expanding the
{.format} part into something like {format:\.[a-z]+}, however the Pylons
route also matches URLs with no extension (eg /something/name). A more
conditional pattern like {format:(\.[a-z]+)?} has nothing to anchor to, so
the {name} part claims the whole string. The only other option I can think
of is to duplicate the routes (and the view_config), however the
application has about 300 routes already, so this would be painful and
ugly. Cleaning up the API presented by the application is also not viable -
I don't control all the client code. At this stage, I'm considering
implementing a view_config replacement that autogenerates routes (hiding
the painful and ugly). Does anyone have any better suggestions?
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/8703ad42-5e87-497f-95a2-b7e9e43e8840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
