-
Notifications
You must be signed in to change notification settings - Fork 131
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
Use of memcache is a blocker to Python 3.7 migration #1371
Comments
I think re-coding to use Cloud Firestore for Datastore might be the way to go for a replacement. |
It's happening.. I guess we could just drop it for now :) These days I was thinking about the whole migration plan.. I guess we could do it in steps.. WDYT? |
Google suggest migrating service by service everything in the google.appengine namespace, then making the code py2/py3 compatible. Then the jump to py3 should be very easy. |
Hi!. Is there any evolution in the code to migrate to python3? you who are already aware of the needs, could you tell us at what points we can help in this migration? are any of the forks already advanced in this perhaps? |
@proudhon - I don't think there has been any evolution in the migration to python3. I'm sure any help would be welcome. I think there are probably six issues that need to be dealt with, and they are mostly independent of each other, so you could dive into any of them that you were interested in. I think doing (1) first would make it slightly easier though. Consulting https://cloud.google.com/appengine/docs/standard/python3/python-differences will be useful.
|
main/cache.py
uses memcacheThis is not available in the Python 3.7 runtime.
Google suggests using Memorystore for redis, but this has no free tier, and gae-init is intended to work within the free tiers.
The text was updated successfully, but these errors were encountered: