Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update webapp2 auth for standard GAE Python3 #137

Open
fili opened this issue Sep 13, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@fili
Copy link

commented Sep 13, 2018

The new standard GAE uses Python3, but does not use:

Memcache

Prefers Firestore over Datastore

Does not support Users API

It is still possible to use webapp2 with the new standard GAE Python3, as an example can be found here: https://bitbucket.org/fili/gae-standard-python37-webapp2-example/src

But the overall integration with GAE services are gone and unlikely to ever come back. It would be best to update the code base to be more independent from GAE old services, or support at least all the different Google Cloud database solutions.

@fili fili changed the title Update webapp2 for Standard GAE Python3 Update webapp2 auth for Standard GAE Python3 Sep 13, 2018

@fili fili changed the title Update webapp2 auth for Standard GAE Python3 Update webapp2 auth for standard GAE Python3 Sep 13, 2018

@theacodes

This comment has been minimized.

Copy link
Member

commented Sep 13, 2018

Hi, thanks for filing this issue.

Just a heads up - webapp2 is a community-supported project. Someone in the community will need to volunteer to do this. I am happy to review and merge any pull requests.

@AniX

This comment has been minimized.

Copy link

commented Sep 13, 2018

In other words, everything in webapp2_extras/appengine/ can't be used anymore? I believe the same is true for the flexible environment.

Are these modifications supposed to be part of webapp2 3.0.0?

@fili

This comment has been minimized.

Copy link
Author

commented Sep 14, 2018

Well the difference is that it depends on the database solution you choose. When you create a new project, you get the question if you want the future Firestore as a database solution OR Cloud Datastore, with the latter it may still be possible to create a workable solution with minimal code changes but NDB is not supported in flex.

Once you pick a database solution, you can not use the other solution anymore within the same project. And as Firestore is likely to replace Cloud Datastore - based on the documentation I have read so far it is probably best to either upgrade webapp2 to include the Firestore option OR to make the code database solution independent so any database solution (including for example Cloud SQL) would work using adapters or something alike.

@kits-ragh

This comment has been minimized.

Copy link

commented Feb 25, 2019

I have used webapp2 in my application, Now I am migrating my application in python3, but it gets fail.

Is there any timeline to get the python3 compatible with webapp2 framework.

@fili

This comment has been minimized.

Copy link
Author

commented Feb 25, 2019

The latest version of webapp2 runs on python3. See also https://bitbucket.org/fili/gae-standard-python37-webapp2-example

@fili

This comment has been minimized.

Copy link
Author

commented Feb 25, 2019

The problem is that webapp2 has a lot of legacy code for connecting with ndb etc, which is now outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.