On Friday, June 5, 2015 at 10:17:36 PM UTC+2, Rufus wrote: > > On Friday, June 5, 2015 at 3:35:08 PM UTC-4, Niphlod wrote: > >> BTW: until all snippets are continously tested, this is going to become >> the 4th incarnation of a "web2py snippet blog/container/etc" with outdated >> pieces of code within the next year, when the buzz wears off. >> > > Nothing worse than getting broken code samples off the web, is there? > (Well, there are worse things...) > Maybe we can add some fields to each snippet to indicate: which versions > it was tested on, when it was > submitted, when last verified, etc. > > I fell off the wagon too many times to trust again a "repository" of sorts of untested thingies. It's the real truth that bites: there's no manpower available and so if something else (a CI) does the job, it pretty much stays viable until the developer that creates it uses it. Then we get angry users here asking for "why is that not working anymore, wasn't web2py supposed to be backward-compatible..." instead of asking the original developer. Once you put it in a plugin, people won't ever be interested in seeing the code, the damn thing needs to work as intended. They get crazier and crazier about it because web2py userbase is not - that - skilled in python: it attracts lots of newbies for that reason and we (the main developers) need to live with that: no feedback in testing, not interested in poking a bit to maintain it/refresh it, huge interest in being just disappointed.
-- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
