Yes, dealing with the embedded web server is out of the scope of the
library and not something that I'd want to introduce. Having said that,
there wouldn't be any harm in a sanction-embedded library that would add
that capability. Thanks for the info.
--
http://mail.python.org/mailman/listinfo/pyt
On Wed, Sep 26, 2012 at 11:45 AM, Demian Brecht wrote:
>>
>> If you are writing a desktop application, read this:
>> https://developers.google.com/accounts/docs/OAuth2#clientside
>
>
> You mean https://developers.google.com/accounts/docs/OAuth2#installed? Your
> link discusses client side browser
>
>
> If you are writing a desktop application, read this:
> https://developers.google.com/accounts/docs/OAuth2#clientside
You mean https://developers.google.com/accounts/docs/OAuth2#installed? Your
link discusses client side browser implementations.
I'd be curious to know the shortcomings of sa
(making no attempt to fix messed up quoting, please take a look at
your mail client configuration)
On Wed, Sep 26, 2012 at 1:52 AM, Littlefield, Tyler wrote:
> On 9/25/2012 2:05 PM, Demian Brecht wrote:
>
> This is a shameless plug, but if you want a much easier to understand method
> of accessin
On 9/25/2012 2:05 PM, Demian Brecht wrote:
This is a shameless plug, but if you want a much easier to understand
method of accessing protected resources via OAuth2, I have a 55 LOC
client implementation with docs and examples
here:https://github.com/demianbrecht/sanction (Google is one of the
This is a shameless plug, but if you want a much easier to understand
method of accessing protected resources via OAuth2, I have a 55 LOC client
implementation with docs and examples here:
https://github.com/demianbrecht/sanction (Google is one of the tested
providers with an access example).
Are
