Re: [pylons-discuss] IDE or na

[Steve Piercy]

I found that using PyCharm's Community Edition (free) helped me 
immensely to learn Python.  Autocompletion is a huge help.  
PyCharm offers a built-in terminal, so if your class requires 
its use, it is there in the IDE.


Additionally the Professional version is free to students and 
teacher of accredited institutions.


https://www.jetbrains.com/pycharm/buy/#edition=discounts

Talk Python training offers several excellent courses for 
learning Python, Pyramid, and PyCharm at a very reasonable price.


https://training.talkpython.fm/

Full disclosure, both entities sponsor Pylons Project and Pyramid.

https://trypyramid.com/community-sponsors.html

--steve


On 6/7/19 at 11:07 AM, jackj.sk...@gmail.com (Joshua Jackson) pronounced:

I want to create a PWA. When using Pyramid, do you recommend 
using an IDE such as Pycharm or some other way? In school we do 
all of our stuff through the command line, so wasn't sure. 
Thank you!





Steve Piercy, Eugene, OR

--
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/r480Ps-10126i-2CA5B4B3BE894E6CAB675E161DE282F2%40Steves-iMac.local.
For more options, visit https://groups.google.com/d/optout.

[pylons-discuss] IDE or na

[Joshua Jackson]

I want to create a PWA. When using Pyramid, do you recommend using an IDE 
such as Pycharm or some other way? In school we do all of our stuff through 
the command line, so wasn't sure. Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/d7534b11-a009-4cbf-9e03-1e3ba2355aa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-discuss] Velruse… or what else?

[Michael Merickel]

On Fri, Jun 7, 2019 at 2:38 AM Jens Troeger  wrote:

> The recent OAuth thread
> 
> recommends requests-oauthlib
> … Can you recommend any
> particular package, is the that one good?
>

I've used requests-oauthlib successfully in the past. I'd recommend it. I
never found much reason to use it during the process of acquiring an access
token, but you can. Once you have an access token and possibly a refresh
token, it serves as a nice wrapper around a requests.Session to handle
adding the appropriate Authorization header as well as assisting in token
expiration and using the refresh token to get new access tokens.

- Michael

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CAKdhhwFnYSgNLW%3Dfac606p86cQLo_QAF8iZ5OgQ%2Bot-uth5MCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-discuss] Velruse… or what else?

[Christian Ledermann]

https://github.com/python-social-auth/social-app-pyramid may be worth a try
(I used https://github.com/python-social-auth/social-app-django with great
success)

On Fri, 7 Jun 2019 at 08:38, Jens Troeger  wrote:

> Thank you Michael for sharing your insights here. I’ve looked through some
> of the code but, as you said, the testing looked rather daunting to me.
>
> On top of that, it's actually really easy (imo) to consume OAuth 2.x +
>> OpenID Connect apis directly. Most bindings for velruse end up being just a
>> very thin wrapper around a small amount of code you can easily write
>> yourself. It basically just involves implementing a redirection endpoint
>> that the provider will send the browser to once the user has granted
>> access, and from there taking the token and querying whatever you want from
>> the provider's api. OpenID Connect has helped a lot in standardizing the
>> type of data you'd want to receive - something velruse was trying to
>> standardize before that standard existed.
>>
>
> This statement of yours aligns nicely with my thoughts/suspicion that
> perhaps I ought to drop Velruse altogether, and instead use an OAuth2
> package to talk with the providers directly. The website uses only Google,
> LinkedIn, Live anyway (and I’m thinking to add Apple now) and they all—I
> think—speak OAuth2.
>
> The recent OAuth thread
> 
> recommends requests-oauthlib
> … Can you recommend any
> particular package, is the that one good?
>
> Much thanks!
> Jens
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To post to this group, send email to pylons-discuss@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/d1292058-f1d9-48a7-8068-e5f290199bf8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Best Regards,

Christian Ledermann

Newark-on-Trent - UK
Mobile : +44 7474997517

https://uk.linkedin.com/in/christianledermann
https://github.com/cleder/


<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CABCjzWooFFaNcCCJnDOvxv13N594J8H0sUVo%2Bc%3DWq55MTEo1SA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-discuss] Velruse… or what else?

[Jens Troeger]

Thank you Michael for sharing your insights here. I’ve looked through some 
of the code but, as you said, the testing looked rather daunting to me.

On top of that, it's actually really easy (imo) to consume OAuth 2.x + 
> OpenID Connect apis directly. Most bindings for velruse end up being just a 
> very thin wrapper around a small amount of code you can easily write 
> yourself. It basically just involves implementing a redirection endpoint 
> that the provider will send the browser to once the user has granted 
> access, and from there taking the token and querying whatever you want from 
> the provider's api. OpenID Connect has helped a lot in standardizing the 
> type of data you'd want to receive - something velruse was trying to 
> standardize before that standard existed.
>

This statement of yours aligns nicely with my thoughts/suspicion that 
perhaps I ought to drop Velruse altogether, and instead use an OAuth2 
package to talk with the providers directly. The website uses only Google, 
LinkedIn, Live anyway (and I’m thinking to add Apple now) and they all—I 
think—speak OAuth2.

The recent OAuth thread 
 
recommends requests-oauthlib … 
Can you recommend any particular package, is the that one good?

Much thanks!
Jens

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/d1292058-f1d9-48a7-8068-e5f290199bf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.