I think that something needs to be doing to keep the principle ("There
should be only one way of doing things").
Some warnings would be a good start. :-)
On 26 out, 14:14, Álvaro Justen [Turicas] <alvarojus...@gmail.com>
wrote:
> On Mon, Oct 26, 2009 at 13:42, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > Good point. web2py can do this
>
> > import logging
> > logging.warn('something is deprecated')
>
> > I could redefine
>
> > SQLDB=lambda *a,**b: logging.warn(...) and DAL(*a,**b)
>
> > this would already produce lots of logs. I would not do it for SQLXyy
> > because that would make even more logs.
>
> I agree.
>
>
>
> > Pros/Cons?
>
> > On Oct 26, 10:37 am, Renato-ES-Brazil <caliari.ren...@gmail.com>
> > wrote:
> >> Massimo,
>
> >> About the question of "backward compatibility", maybe there will come
> >> a time that one of the principles Python and web2py are broken,
> >> specifically this: "There should be only one way of doing things".
>
> >> Or not? :-)
>
> >> Example (extracted from manual):
>
> >> "For backward compatibility SQLDB=DAL and SQLField=Field. We encourage
> >> you to use the new syntax DAL and Field, instead of the old syntax."
>
> >> I think would be interesting display warnings in some log file about
> >> the deprecated methods used in some app. What do you think? Is web2py
> >> already capable of doing that?
>
> >> Thanks. :-)
>
> --
> Álvaro Justen
> Peta5 - Nós fazemos TV Digital!
> 21 3021-6001 / 9898-0141
> http://www.peta5.com.br/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
