On Thursday, June 4, 2015 at 12:25:00 PM UTC-7, Niphlod wrote: > > >> And remember that deprecated is meant to give you time to change over to >> newer stuff, but the deprecated stuff could be removed completely at some >> point. Your '54 Coupe could be banned from freeways or even public roads >> except under special conditions of historic display. >> >>
> not really: let's tune the "scary" bits down a notch. Even if Crud will > expose security flaws, it'll be reported (and probably won't be fixed, > hence the "discontinuation/deprecation" discussion), but web2py being a > "backward-compatible" framework, you'll continue to be able to use it as it > stands. There won't be bans, as Crud is an opt-in . If you want to use it, > use it, but don't ask for new features nor fixes. > Sorry, I was thinking of "deprecated" in terms of other contexts. Mercurial is very much into backwards compatibility, also, but deprecated features there are those that will be dropped in a subsequent release; standards documents tend to use deprecated in that way, too. For them, it's "you can use it for now or if you never upgrade, but new stuff shouldn't use it". /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
