>> Could you explain why TG2 isn't compliant? and why is it a "serious >> bug" ? > > Because it manipulates the named and positional arguments, but doesn't define > them in the relevant variable in the environ.
<<<SNIP>>> > If you want interoperability, then you should follow standards. So this time, > if you want the parameters extracted from TG2's object dispatch stuff to be > usable in TG-independent stuff, then they must be made available in a TG- > independent way -- and there's already an standard for that. Well, TurboGears Root controller is a WSGI app, but tg controller methods are NOT wsgi apps, so I don't think that technically we are doing anything wrong, as we're not officially doing wsgi app dispatch, but choosing methods --within-- a wsgi app and calling them with a totally different signature than the wsgi spec. But, I do think it's a good idea to follow the spec, and it should be pretty easy to make it do that -- this would be a great item for the pycon sprint if we don't get to it before then. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
