On Dec 11, 2007 12:09 AM, Lawrence Oluyede <[EMAIL PROTECTED]> wrote:
>
> On Dec 11, 2007 12:26 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
> >
> > Added "What's New in Pylons 0.9.7?" to the Cookbook, explaining the
> > changes that have been implemented in Pylons' development version.
> > http://wiki.pylonshq.com/pages/viewpage.action?pageId=11174779
>
> Don't mean to criticise but I hoped you would keep some kind of
> compatibility layer in the webob transition with warning messages
> activated.
> It shouldn't be good to search and replace every status_code with
> status_int because they just have different names :-)
> I know WebOb is better, but it's a 0.9 version anyway. Can't you keep
> the same API for compatibility/portability reasons with a warning
> message
> that notifies the user of the complete drop of the old way in Pylons 1.0 or
> so?
>
> Let me know what you thinkg
Actually, WebOb is not activated by default. I should have put that
on the page. To use WebOb
you have to change
app = PylonsApp(use_webob=False)
in middleware.py to True. At some point it will become the default
and the option removed, but
I've forgotten which version Ben said that would be.
If there are warnings (which can be done with Python's warnings module
-- as SQLAlchemy is doing),
they should go into 0.9.7 or 0.9.8. Every version of Pylons has been
dropping old APIs when it's released; otherwise 1.0 will be 50% cruft.
--
Mike Orr <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
