On Monday, March 4, 2013 3:10:33 PM UTC+1, Michele Comitini wrote: > > First of al I like a library that claims web2py compatibility that's a > very good sign! >
? web2py is "out" (part of the reason why I asked if someone was interested). There's webpy, flask and django. > Does social-auth support a common API (aka janrain) to access social > info or it is just the auth part? > seems also extra data > For the auth part we already cover already much of it, the dying > OAuth1.0a and the now stable OAuth2.0,we have also backward > compatibility with the broken facebook implementation. Maintenance > is a relative issue, since these protocols should be rather stable. > That was more or less the big point: what if someone like you leaves the module the way it is and some changes are introduced in the APIs ? Did anyone tested the contrib module against something that was not facebook, google or linkedin ? There are 44 backends already tested with that module. We have 6 contrib modules for managing various oauth implementations and most of it remains probably untested (there are no unittest available for all of them)... <rant mode="good way ^_^"> At the end of the day..... why should web2py reinvent the wheel every time (this is only an example) instead of relying on battle-tested libraries ? Less code to include in the distribution, less code to maintain, more users to test the features (testers for web2py modules and contribs are REAAAAALLY lacking), less probability that if the maintainer has something else to do the code would be updated anyway. </rant> -- --- 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/groups/opt_out.
