Re: [google-appengine] Migrating Python 2 to 3: images

['Andrew Gorcester' via Google App Engine]

The migration guide does have a brief section in the overview:
https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services
which
suggests migrating to third-party image services. However, depending on
your use case (keeping in mind impacts on security and performance) you may
find it more suitable to install a library which performs the operation
in-place on your App Engine instance. Pillow is one I have used in the past.

On Mon, Feb 24, 2020 at 12:18 PM Joshua Smith 
wrote:

> I need to read and resize an image in my google app engine app. In my
> python2.7 code, this is simply:
>
> from google.appengine.api import images
> image = images.resize(image, width=1024, output_encoding=images.JPEG,
> correct_orientation=images.CORRECT_ORIENTATION)
>
> I can’t find anything the migration guide that suggests an alternative to
> this API (but several places say I need to find one). So helpful.
>
> What does this august body recommend I use to replace the above two lines
> of code? I certainly don’t want to have to use some web-based micro-service
> for such a simple thing.
>
> -Joshua
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/DA44AE42-4D42-47C1-BE0B-9726516FF865%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJtX7KbauQa9nFwpJzOHCDLTKRTG_eSRiz8bfGJ5sU7Pg%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

I'm afraid none of the Cloud API-targeting libraries have testbed support,
as testbed was a solution to App Engine Gen 1-specific problems at the
time. If you have an example of how much slower the datastore emulator is
vs. testbed for your use case, that would be very helpful in prioritizing
further work, either in speeding up the emulator or replicating the testbed
system for Cloud. I'd recommend filing a bug with your experiences at
https://github.com/googleapis/python-ndb/issues (though this would
eventually be tackled by the entire Cloud Client libraries team, rather
than just the NDB team).

On Mon, Feb 24, 2020 at 1:05 PM Remko Tronçon  wrote:

> On Monday, February 24, 2020 at 9:52:25 PM UTC+1, Andrew Gorcester wrote:
> > Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend
> tests be done using that, the same way on Cloud NDB as they would be with
> the Cloud Datastore library.
>
> Using an external emulator is way too slow to use for unit tests, even if
> you are able to get all your code changed so you don’ have to tear down and
> clean start the emulator to avoid interference between tests. This is
> pretty disappointing, and means I (and I expect many others) will be forced
> to rewrite everything if your app isn’t in pure maintenance mode.
>
> Remko
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/9f3246de-d324-4e33-b2d9-86f00a642aa5%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJY3MAHgOkknEm8WLEFq5-eXQLZwL%3DZ4Dt5G-LU6%3DyicA%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Cloud NDB is intended as a migration tool for App Engine NDB users who wish
to move to either newer versions of App Engine (App Engine Python 3) or to
other environments. Customers are welcome to use Cloud NDB however they
wish, including on totally new projects that aren't associated with GAE
NDB. However, Cloud NDB will not add support for any new features that
might be added to Cloud Datastore in the future, because that wouldn't
further the goal of aiding migration from GAE NDB; also the NDB concurrency
model was designed around GAE Python 2.7 limitations and might not be the
best model for greenfield projects with no history rooted in App Engine. We
recommend the use of the Cloud Datastore library for new projects when
possible.

On Mon, Feb 24, 2020 at 12:08 PM Philip  wrote:

> In this ticket  it
> was stated that Google does not recommend NDB for new projects. It is
> merely intended for upgrading from 2.7 to python 3 GAE. It this statement
> still true given the fact that it is now GA?
>
> Am Montag, 24. Februar 2020 20:02:36 UTC+1 schrieb Andrew Gorcester:
>>
>> Hello Pythonistas,
>>
>>
>> The Cloud NDB client library for Cloud Datastore and Cloud Firestore in
>> Datastore mode, previously introduced as a beta project in September 2019,
>> has been launched to GA with its 1.0 release.
>>
>>
>> Cloud NDB is an updated version of the App Engine NDB client library for
>> Datastore, adding support for Python 3 and targeting the Datastore API.
>> While it is intended for users migrating from App Engine Python 2.7 to App
>> Engine Python 3, it is fully portable and compatible with other Python
>> platforms. The library can be installed with `pip install google-cloud-ndb`
>> and the source code can be found on Github at
>> https://github.com/googleapis/python-ndb.
>>
>>
>> We also have a migration guide for NDB
>> 
>> at, as part of our broader GAE Python migration documentation
>> .
>> We'll continue updating and adding to this documentation and library as
>> part of our migration support effort, so please also continue sending us
>> your feedback.
>>
>>
>> Thank you again for your continued support for App Engine and our Cloud
>> platform. I am looking forward to hearing feedback from the community on
>> this and upcoming efforts.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/322768f1-6716-436c-b4da-e8d17ed4ad77%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLs3NzYfuVxa8vkvt8oQNWeSt_c%3Ds%2BGUcU4QL18gNz1Cw%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend
tests be done using that, the same way on Cloud NDB as they would be with
the Cloud Datastore library.

On Mon, Feb 24, 2020 at 11:59 AM Remko Tronçon  wrote:

>
> We also have a migration guide for NDB
>> 
>> at, as part of our broader GAE Python migration documentation
>> .
>> We'll continue updating and adding to this documentation and library as
>> part of our migration support effort, so please also continue sending us
>> your feedback.
>>
>
> The migration guide doesn't mention how NDB unit tests can be ported.
> AFAIK, the testbed that is currently available in NDB is not available for
> Cloud NDB.
> Is there anything provided for unit testing Cloud NDB code, or do you have
> to abstract out NDB (which sounds like a huge effort and would pretty much
> make Cloud NDB useless).
>
> thanks,
> Remko
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/307e34e9-60ed-4534-a330-1adbad15255a%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK_%3D5ibcb6UML-8wDeog0rDQ_0j%2BnR_fuLaytw4QfMCQQ%40mail.gmail.com.

[google-appengine] Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,


The Cloud NDB client library for Cloud Datastore and Cloud Firestore in
Datastore mode, previously introduced as a beta project in September 2019,
has been launched to GA with its 1.0 release.


Cloud NDB is an updated version of the App Engine NDB client library for
Datastore, adding support for Python 3 and targeting the Datastore API.
While it is intended for users migrating from App Engine Python 2.7 to App
Engine Python 3, it is fully portable and compatible with other Python
platforms. The library can be installed with `pip install google-cloud-ndb`
and the source code can be found on Github at
https://github.com/googleapis/python-ndb.


We also have a migration guide for NDB

at, as part of our broader GAE Python migration documentation
.
We'll continue updating and adding to this documentation and library as
part of our migration support effort, so please also continue sending us
your feedback.


Thank you again for your continued support for App Engine and our Cloud
platform. I am looking forward to hearing feedback from the community on
this and upcoming efforts.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLfFqve1kvcUustO%3DjdsS%2ByLO-eOW1bOsQ2kqb3Yk2CnA%40mail.gmail.com.

Re: [google-appengine] Trouble to deploy and download dependencies

['Andrew Gorcester' via Google App Engine]

That message from pycrypto is misleading. xcode is only needed on osx. For
Windows you need a different way to install a C compiler. If you are using
Cygwin, there should be a Cygwin package for a compiler such as gcc
available but I'm afraid I am not certain about the details.

On Thu, Feb 13, 2020, 6:18 AM Dongcheng Li  wrote:

> Thank you. It passed this step. However, another issue appear
>
> Windows is now supported as of version 1.11. In the scripts directory,
> there are two batch files:
>
>- windows_start_local.bat starts a local dev server so you can explore
>Course Builder in your browser for testing.
>- windows_deploy.bat deploys your application to Google App Engine.
>
> Note: If you have an older version of Windows, you may need to manually
> download Cygwin <https://www.cygwin.com/>. Watch the terminal for errors
> and instructions.
>
> When I run  windows_start_local.bat   OR  windows_deploy.bat,  the window
> of Command Prompt showed
> [image: image.png]
>
> I am wondering how I can run $ xcode-select --install from Command Prompt.
>
> Thank you for your help.
>
> DC
>
>
>
>
> On Wed, Feb 12, 2020 at 5:17 PM 'Andrew Gorcester' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> Hi, you're probably looking at the Course Builder documentation on a
>> windows machine, right? You can install Cygwin, or if you have Windows 10,
>> you can instead install Windows Subsystem for Linux, and that should get
>> you a command prompt from which you can run bash without issue.
>>
>> On Wed, Feb 12, 2020, 1:45 PM Dongcheng Li  wrote:
>>
>>>
>>> Before you deploy, ensure you have all the things (like libraries, other
>>> software) you need to be successful. The deploy script mentioned in the
>>> section below will try to download any dependencies also, but in this step
>>> you will get more messages about the process. These messages may help you
>>> if anything is wrong. To download dependencies, open a command prompt and
>>> get to your coursebuilder directory. Type the following command:
>>>
>>> bash ./scripts/common.sh
>>>
>>>
>>> I am stuck on this step. After type this command, it showed
>>>
>>> [image: 1581542250(1).png]
>>>
>>> Does anyone know what caused it? Any clue? Thanks.
>>>
>>> DC
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-appengine+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-appengine+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CALkCzHZM%3DpsOuSQuwRLYMcipy%3D_FDkoPirKS-DZujrph-Yae%3DA%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-appengine/CALkCzHZM%3DpsOuSQuwRLYMcipy%3D_FDkoPirKS-DZujrph-Yae%3DA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2Bh6P9eL2ouRXxfQ65-13X_JGZVFgYy0rqmAoaMVvZqFQ%40mail.gmail.com.

Re: [google-appengine] Trouble to deploy and download dependencies

['Andrew Gorcester' via Google App Engine]

Hi, you're probably looking at the Course Builder documentation on a
windows machine, right? You can install Cygwin, or if you have Windows 10,
you can instead install Windows Subsystem for Linux, and that should get
you a command prompt from which you can run bash without issue.

On Wed, Feb 12, 2020, 1:45 PM Dongcheng Li  wrote:

>
> Before you deploy, ensure you have all the things (like libraries, other
> software) you need to be successful. The deploy script mentioned in the
> section below will try to download any dependencies also, but in this step
> you will get more messages about the process. These messages may help you
> if anything is wrong. To download dependencies, open a command prompt and
> get to your coursebuilder directory. Type the following command:
>
> bash ./scripts/common.sh
>
>
> I am stuck on this step. After type this command, it showed
>
> [image: 1581542250(1).png]
>
> Does anyone know what caused it? Any clue? Thanks.
>
> DC
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com.

Re: [google-appengine] Pull Queue Deprecation?

['Andrew Gorcester' via Google App Engine]

App Engine Tasks (available for App Engine Standard Gen 1 runtimes) will
continue to support both push and pull, but Cloud Tasks (available for all
products) will not support pull queues. Instead, we recommend Cloud Pub/Sub
for this use case. Please see this documentation for details:
https://cloud.google.com/appengine/docs/standard/java/taskqueue/pull/migrating-pull-queues

Please let us know if Cloud Pub/Sub doesn't solve your needs in this area,
so we can improve our decisions for future features.

On Fri, Jan 10, 2020 at 11:10 AM Jim  wrote:

> I have an app running on Google App Engine Standard using the Java 8
> runtime, and it uses both push and pull queues extensively.  When I'm using
> the Google Cloud Platform management console I interact with my Push and
> Pull Queues under the "Cloud Tasks" UI option, but all of my code
> interaction with queues is via the com.google.appengine.api.taskqueue Java
> package.  Lately I'm seeing notices about Google Cloud Tasks Pull Queues
> being deprecated.  Can someone in the GAE team please clarify for me, will
> my usage of Pull Queues be supported going forward?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/588d3ad9-03f8-47c1-afa2-f2b4d993caae%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK3YMkOrsVYjcJJzX06gic4-eHJZ79j8d_RmpRtHsrawQ%40mail.gmail.com.

Re: [google-appengine] Re: App Engine, MySQL and private ip

['Andrew Gorcester' via Google App Engine]

Hi Charlotte,

Additionally, once you have a private Cloud SQL IP address, I think you
should be able to connect to it from App Engine by using Serverless Virtual
Private Cloud Access:
https://cloud.google.com/vpc/docs/configure-serverless-vpc-access .

On Wed, Dec 4, 2019 at 3:32 PM 'Elliott (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Charlotte,
>
> You can get a private IP when you create a Cloud SQL instance under
> “Configuration Options”. I hope this helps.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/58f84428-a784-4f58-8aea-c739eaad316b%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2B9kXcMbWfWrJLX_rPDoAnBXidDoH_rD5j%3D0P-koxbwew%40mail.gmail.com.

Re: [google-appengine] Python 3.7 and Python 2 ndb cache conflict

['Andrew Gorcester' via Google App Engine]

Hi Eliran,

On Python 3, you can use Cloud Memorystore to provide a Redis cache.
However, you can't currently share a cache between the Python 2.7 and
Python 3.7 versions of the GAE. The cache will be separate, which will be
an issue as you describe if you are running both Python 2 and Python 3
versions targeting the same Datastore database.

Now that Cloud NDB supports Python 2.7 in addition to Python 3.7, you could
try to solve this problem by replacing your GAE NDB with Cloud NDB on
Python 2.7, and then pointing it at the same Redis instance as the Python
3.7 version. Instead of sharing Memcache, you can share Redis. See the
documentation for more info:
https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb

On Wed, Dec 4, 2019 at 5:20 AM 'Eliran Segev' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hi, we are migrating our python 2 services to python 3.
>
>
> In python 2 we are using NDB - that uses Memcache
> In python 3 we are using cloud NDB - that cannot have Memcache as cache
> provider
>
> And now we have a problem when updating an entity from Python 3 it does
> not affect the cache, and when using Python 2 we get the cached copy of
> this entity.
>
>
> Without changing python 2 code to cloud NDB, how can we solve this and
> still have cache?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/19ecce3c-e774-491f-a168-40b99393c651%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLerNxFOi7-6T_9aNpJzD0KqDmoimNAJ%2Bm3PSmxTmi3uQ%40mail.gmail.com.

Re: [google-appengine] Re: GAE Standard | Local Dev | Python37: google.appengine.api not found

['Andrew Gorcester' via Google App Engine]

Unfortunately there is not currently any Google Cloud replacement for the
GAE Mail API. We are aware of the gap in our migration story and are
working to fix it.

On Mon, Nov 25, 2019, 5:44 PM Yanay Lehavi  wrote:

> Thank you Andrew. We have migrated most of our stuff to py37 and
> everything works very well so far. I'm familiar with the documentation. The
> reason I started this thread is I'm trying to migrate automated email
> (which in 27 call the appengine.api package). It looks like there's no way
> to send email under 37?
>
> Thanks!
>
> On Monday, November 25, 2019 at 12:00:22 PM UTC-8, Andrew Gorcester wrote:
>>
>> Hi Yanay,
>>
>> I'm an engineer at Google working on making the migration from GAE Python
>> 2.7 (a Gen 1 runtime) to Python 3.7 (a Gen 2 runtime) clearer for users. In
>> addition to the page Ryan linked above which explains the differences, we
>> have also recently published this migration homepage with some tutorials
>> and examples:
>> https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/
>>
>> Please take a look and let us know if you need more specific information.
>> Thanks!
>>
>> On Mon, Nov 25, 2019 at 9:58 AM Ryan B  wrote:
>>
>>> hi Yanay! the classic App Engine APIs in google.appengine.api aren't 
>>> available
>>> in the Python 3 runtime. More details:
>>> https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
>>>
>>>
>>> On Sunday, November 24, 2019 at 6:08:57 PM UTC-8, Yanay Lehavi wrote:

 I see a number of threads on this in git etc. but they all seem
 unresolved:

 >>> import google.appengine.api

 Traceback (most recent call last):

   File "", line 1, in 

 ModuleNotFoundError: No module named 'google'

 >>>

 In the above mentioned threads, some people suggested various env vars,
 none of which I have, nor ever needed... (been developing GAE locally for a
 long time).
 My platform: Mac Catalina.
 Anyone knows how to resolve this?
 Many thanks

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-a...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/5ee38ced-fcd4-4f8f-bf80-2e1b4b51338f%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJd8BMzetwv3omnF4XnQZ639-vtsBqF0f_TJ_f0%3DU9PcQ%40mail.gmail.com.

Re: [google-appengine] Re: GAE Standard | Local Dev | Python37: google.appengine.api not found

['Andrew Gorcester' via Google App Engine]

Hi Yanay,

I'm an engineer at Google working on making the migration from GAE Python
2.7 (a Gen 1 runtime) to Python 3.7 (a Gen 2 runtime) clearer for users. In
addition to the page Ryan linked above which explains the differences, we
have also recently published this migration homepage with some tutorials
and examples:
https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/

Please take a look and let us know if you need more specific information.
Thanks!

On Mon, Nov 25, 2019 at 9:58 AM Ryan B  wrote:

> hi Yanay! the classic App Engine APIs in google.appengine.api aren't available
> in the Python 3 runtime. More details:
> https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
>
>
> On Sunday, November 24, 2019 at 6:08:57 PM UTC-8, Yanay Lehavi wrote:
>>
>> I see a number of threads on this in git etc. but they all seem
>> unresolved:
>>
>> >>> import google.appengine.api
>>
>> Traceback (most recent call last):
>>
>>   File "", line 1, in 
>>
>> ModuleNotFoundError: No module named 'google'
>>
>> >>>
>>
>> In the above mentioned threads, some people suggested various env vars,
>> none of which I have, nor ever needed... (been developing GAE locally for a
>> long time).
>> My platform: Mac Catalina.
>> Anyone knows how to resolve this?
>> Many thanks
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLu%3D2S%2B_w_et%2B35QOaM_w7R6J-JiB%2BDcoVMXcy7s1S%3DNg%40mail.gmail.com.

Re: [google-appengine] Django Channels Support in Google App Engine

['Andrew Gorcester' via Google App Engine]

Websockets are supported on Google App Engine Flexible Environment. They
are not supported on Standard Environment at this time.

On Tue, Nov 19, 2019, 6:50 PM Ranjan Barat  wrote:

> Hello All, Please help us in understanding if we have support for Django
> Channels & WebSockets support in Google App Engine, if not, then whats best
> available solution
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/6bdeb497-0273-4da8-bfc2-fcb578d48798%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJwXKmR8xPJez31-%3DMXrURrQ9oaOzH9AFCNx6o7-9Yr9A%40mail.gmail.com.

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

['Andrew Gorcester' via Google App Engine]

That does make sense. If you could bridge the gap by using a single static
file directory in app.yaml served with a single static_dir handler, that
might work too. But I know some apps have very complex app.yaml defined
static files, so I understand why you're looking at the dev_appserver.py
option instead.

On Fri, Nov 8, 2019 at 3:33 PM Ryan Barrett  wrote:

> thanks for the reply!
>
> On Fri, Nov 8, 2019 at 2:40 PM 'Andrew Gorcester' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> I would recommend trying to solve the first problem and serving static
>> files locally.
>>
>
> understood, but using a different static file server is not great. it
> makes local development diverge significantly from production. local no
> longer uses or tests app.yaml's static file handlers, but prod does, so
> bugs will eventually pop up that only happen in production, and are thus
> harder to test for and debug.
>
> for that reason, i'm actually going the other way and using dev_appserver
> right now, soi still have some confidence that my app will behave more or
> less the same in production that it does locally. the minute long delay on
> startup is definitely painful though.
>
>
> At first glance I think the most straightforward ways to do that would be
>> to either:
>>
>> - Use the Flask development server instead of gunicorn and leverage
>> Flask's integrated /static directory
>> https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
>> - If you prefer to use gunicorn or you need more serving options, add
>> WhiteNoise middleware to your app; ideally, have your app detect whether
>> it's running in production or in development mode and conditionally add
>> WhiteNoise in development only: http://whitenoise.evans.io/en/stable/
>>
>>
>> On Fri, Nov 8, 2019 at 2:21 PM Ryan B  wrote:
>>
>>> Hi all! My Python 3 topic for the day is local development. How are you
>>> all doing it? Any tips?
>>>
>>> The two main ways seem to be a third party server, eg Flask or Gunicorn,
>>> or dev_appserver.py. I have both working, but each one has a fatal flaw
>>> that makes it basically unusable for me so far.
>>>
>>> When I run my app with eg gunicorn -b :8080 app:application - the way
>>> Google recommends
>>> <https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app#running_locally>
>>> - it works, but doesn't serve any assets from static file handlers in my
>>> app.yaml. This is widely reported on StackOverflow
>>> <https://stackoverflow.com/search?q=%5Bgoogle-app-engine%5D+%5Bpython-3.x%5D+static>
>>> and elsewhere. Responses are often some variation of, "why do you need
>>> static assets for dynamic requests?" The obvious reason is that pretty much
>>> all webapps use images, CSS, and/or JS, among other static files. They're
>>> generally not usable without those assets.
>>>
>>> When I run my app with  dev_appserver.py, it creates a new virtualenv
>>> and installs all of my dependencies from requirements.txt. This is
>>> nice, but also extremely slow for any nontrivial app. My current medium
>>> sized app has 155 packages, and even when they're all cached locally,
>>> installing them takes around 60s. I often switch between different apps and
>>> other stacks, so I can't often keep dev_appserver running for hours or days
>>> on end to avoid this. (I've filed this feature request for
>>> dev_appserver to reuse an existing virtualenv.
>>> <https://issuetracker.google.com/u/1/issues/144150446>)
>>>
>>> Let me know if you have any ideas!
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-appengine+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-appengine/BJDE8y2KISM/unsubscribe
>> .
>> To unsubscribe from this group

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

['Andrew Gorcester' via Google App Engine]

Hi Ryan,

I would recommend trying to solve the first problem and serving static
files locally.

At first glance I think the most straightforward ways to do that would be
to either:

- Use the Flask development server instead of gunicorn and leverage Flask's
integrated /static directory
https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
- If you prefer to use gunicorn or you need more serving options, add
WhiteNoise middleware to your app; ideally, have your app detect whether
it's running in production or in development mode and conditionally add
WhiteNoise in development only: http://whitenoise.evans.io/en/stable/


On Fri, Nov 8, 2019 at 2:21 PM Ryan B  wrote:

> Hi all! My Python 3 topic for the day is local development. How are you
> all doing it? Any tips?
>
> The two main ways seem to be a third party server, eg Flask or Gunicorn,
> or dev_appserver.py. I have both working, but each one has a fatal flaw
> that makes it basically unusable for me so far.
>
> When I run my app with eg gunicorn -b :8080 app:application - the way
> Google recommends
> 
> - it works, but doesn't serve any assets from static file handlers in my
> app.yaml. This is widely reported on StackOverflow
> 
> and elsewhere. Responses are often some variation of, "why do you need
> static assets for dynamic requests?" The obvious reason is that pretty much
> all webapps use images, CSS, and/or JS, among other static files. They're
> generally not usable without those assets.
>
> When I run my app with  dev_appserver.py, it creates a new virtualenv and
> installs all of my dependencies from requirements.txt. This is nice, but
> also extremely slow for any nontrivial app. My current medium sized app has
> 155 packages, and even when they're all cached locally, installing them
> takes around 60s. I often switch between different apps and other stacks,
> so I can't often keep dev_appserver running for hours or days on end to
> avoid this. (I've filed this feature request for dev_appserver to reuse
> an existing virtualenv.
> )
>
> Let me know if you have any ideas!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BPRh3vU%3Dpp3708sRAFE8%2BYxC%3Dm%2BmC8oGVqHyLw3yKBhw%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB Datastore library Beta

['Andrew Gorcester' via Google App Engine]

After consulting with product management, I can clarify that Cloud NDB will
be treated the same as other Cloud Client libraries on github and so is not
covered explicitly by our Cloud Support contract, though I'm not personally
familiar with our support contract language so I can't go into any greater
detail.

On Thu, Sep 26, 2019 at 8:05 PM 'Mario Jimenez Leon' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> This is great news!
>
>
>
> The library is gonna be supported by GCP support until the beta phase
> ends. You can track the changes in the changelog of the library in github:
> https://github.com/googleapis/python-ndb/blob/master/CHANGELOG.md
>
>
>
> Currently, we don't have an Estimated Time of Arrival for the new version.
>
>
> On Thursday, September 26, 2019 at 1:01:48 AM UTC-5, Soeren Balko wrote:
>>
>> Great news and good to see Google (finally!) reacting to the Python 2 EOL
>> dilemma and its repercussions on AppEngine!
>>
>> A couple of question though:
>>
>> (1) "beta" is not very reassuring in a sense that we have millions of
>> users in our AppEngine/DataStore backend. When will the library come out of
>> beta?
>> (2) Does the library come under Google Cloud support contracts?
>>
>> Thank you,
>> Soeren
>>
>>
>> On Friday, September 20, 2019 at 7:33:38 AM UTC+10, Andrew Gorcester
>> wrote:
>>>
>>> Hello Pythonistas,
>>>
>>> I'm pleased to announce the Beta release of Cloud NDB, an updated
>>> version of the App Engine NDB client library for Datastore to support the
>>> GAE Python 3 runtime and other Python platforms. Our goal with Cloud NDB
>>> and related efforts is to ensure App Engine Python 2.7 applications are
>>> fully portable and can smoothly migrate to Python 3.
>>>
>>> The library can be installed with `pip install google-cloud-ndb` and the
>>> source code can be found at https://github.com/googleapis/python-ndb.
>>> Please refer to our newly published migration guide at
>>> https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb,
>>> and our API documentation at
>>> https://googleapis.dev/python/python-ndb/latest/index.html.
>>>
>>> We're grateful to have received generous user support in testing,
>>> comments, bug reports and even code contributions in our Alpha phase, and
>>> we hope the community will continue to send feedback as we work towards GA.
>>> Please see our GitHub repository linked above to follow development and
>>> communicate with our team, or email me directly at gorc...@google.com.
>>>
>>> While Cloud NDB can be used freely by any Cloud Datastore (and Firestore
>>> in Datastore mode) customers, it is intended to facilitate migration to
>>> Python 3 for App Engine NDB users; our recommendation for new apps is still
>>> to use the Cloud Client Datastore or Firestore libraries which are part of
>>> the Google Cloud SDK.
>>>
>>> Thanks for your continued support of our platform. I am looking forward
>>> to hearing from the community on this and upcoming efforts.
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/83877d90-87e6-46ea-8b9a-39b3e68e1c16%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFKOs7Qa8g0Eac3Y9qoFO2m-f8k1SPMwPS-i%3DkWnz5ACfQ%40mail.gmail.com.

[google-appengine] Cloud NDB Datastore library Beta

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,

I'm pleased to announce the Beta release of Cloud NDB, an updated version
of the App Engine NDB client library for Datastore to support the GAE
Python 3 runtime and other Python platforms. Our goal with Cloud NDB and
related efforts is to ensure App Engine Python 2.7 applications are fully
portable and can smoothly migrate to Python 3.

The library can be installed with `pip install google-cloud-ndb` and the
source code can be found at https://github.com/googleapis/python-ndb.
Please refer to our newly published migration guide at
https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb,
and our API documentation at
https://googleapis.dev/python/python-ndb/latest/index.html.

We're grateful to have received generous user support in testing, comments,
bug reports and even code contributions in our Alpha phase, and we hope the
community will continue to send feedback as we work towards GA. Please see
our GitHub repository linked above to follow development and communicate
with our team, or email me directly at gorces...@google.com.

While Cloud NDB can be used freely by any Cloud Datastore (and Firestore in
Datastore mode) customers, it is intended to facilitate migration to Python
3 for App Engine NDB users; our recommendation for new apps is still to use
the Cloud Client Datastore or Firestore libraries which are part of the
Google Cloud SDK.

Thanks for your continued support of our platform. I am looking forward to
hearing from the community on this and upcoming efforts.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK8O7YH2gaDCSUQ7vVeM2%3DWoTR%3DXBAz%3DgkFZmbt4oatQQ%40mail.gmail.com.

Re: [google-appengine] Re: Brazil IP

['Andrew Gorcester' via Google App Engine]

Hi Manu,

My observation in the past is that IP geolocation from third party services
is generally not accurate for cloud servers. The server and egress points
are still located in South America as advertised and will have low latency
to South American clients. Unfortunately there is no reliable way that I
know of to control what third party geolocation services report as the
estimated location of the IP address.


On Wed, Aug 28, 2019, 2:16 AM Manu Campos  wrote:

> Hi,
> My VM zone is southamerica-east1-b, but the external IP I received is
> 35.199.93.41 which is located in California.
> I need an IP from Brazil.
> Can you help me?
>
>
> 
>  Livre
> de vírus. www.avast.com
> .
> <#m_2297655411792827469_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> Em ter, 27 de ago de 2019 às 13:38, 'George (Cloud Platform Support)' via
> Google App Engine  escreveu:
>
>> Hello Manu,
>>
>> To get an IP from Brazil, you have the option to choose region
>> southamerica-east1 a, b, c Osasco (São Paulo), Brazil, from the Regions and
>> Zones list .
>> Practical details are to be found on the "Reserving a Static External IP
>> Address" documentation page
>> .
>> It may be worthwhile reading related information on the "Best practices for
>> Compute Engine regions selection" page
>> 
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-appengine+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/ac7c35d7-bf87-4759-a3c7-0423bfa232e8%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CACSgnbOWE-6wXiHW8udyS-2kAggrKy3GPtKzhDXkXjNi2GUkcQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLazdAwkxdSF82UeGzCd_-HyzVhmHy3kH_e_P7wp6ef2A%40mail.gmail.com.

Re: [google-appengine] Re: Source Code download from GAE Flex

['Andrew Gorcester' via Google App Engine]

As a workaround, may I suggest enabling debug mode and SSHing into a
running instance to inspect the filesystem directly? You might be able to
exfiltrate the code manually.
https://cloud.google.com/appengine/docs/flexible/python/debugging-an-instance

On Tue, Aug 20, 2019 at 10:16 AM 'Nicolas (Google Cloud Platform Support)'
via Google App Engine  wrote:

> Hi Sai,
>
> It used to be possible to download your source code with the appcfg.py
> tools but unfortunately this tool is now deprecated and it’s replacement,
> the Cloud SDK   does not support this
> feature.
> There is a feature request for this, and you can follow their progress
> here , although there is no
> ETA for when it will be implemented.
>
> On Monday, August 19, 2019 at 6:26:58 PM UTC-4, Sai M wrote:
>>
>> Hello,
>>
>> By accident i have lost the data on my personal laptop where i have kept
>> the Source code of the project i have deployed on Google App Flex.
>> Unfortunately i don't have the backup as it happened by accident when i was
>> trying to upgrade my OS.
>>
>> The Project ID is..."smartcc".
>>
>> Can you pls. help on instructions of how to down load the latest
>> application source code deployed on Google App Flex env please.
>>
>> Thanks a ton in advance.
>>
>> Best Regards
>> Sai
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/e52822af-78fd-45dc-97d1-4a72915fe6ef%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFKkbxfDY6kXoXB_-E8n8HB_C_o1LM217PbYRXmTEoVhDg%40mail.gmail.com.

Re: [google-appengine] Re: Install Redis Slave on App Engine Flex

['Andrew Gorcester' via Google App Engine]

May I suggest using a custom runtime? You should be able to install and
configure Redis using the Dockerfile system.
https://cloud.google.com/appengine/docs/flexible/custom-runtimes/

On Fri, Jul 26, 2019 at 12:05 PM 'Biswajit Mukhopadhyay' via Google App
Engine  wrote:

> I want a read replica (Redis Slave) to be installed in all App Engine Flex
> instance. Reading from local will increase the performance of the app than
> reading from Memory Store Redis (Reading operation of our app is much
> higher than writing operation). Memory Store Redis will be used as a Master
> and write operation will happen on that Master.
>
>
> On Friday, July 26, 2019 at 8:39:01 PM UTC+5:30, Julie (cloud platform
> support) wrote:
>>
>> You can connect Memorystore for redis with App Engine Flex using this
>> example
>> and
>> if you would like high availability
>>  for
>> Memorystore it is available for Redis instances with the Standard
>> Tier configuration. To clarify, do you want the Redis replica to be
>> connected to it's App Engine Flex instance or Memorystore for Redis as if
>> you are interested in the latter, high availability
>> 
>> cannot be used as a read replica.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/212ed959-6549-4abc-87f1-ebcf3c2a3ea4%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BmUZNW_b0SG4eKtV56jt2oTzmOtafdn6XnhucukYZ9SQ%40mail.gmail.com.

Re: [google-appengine] Re: No Pull Queues for Node.js Standard Environment?

['Andrew Gorcester' via Google App Engine]

Pardon my interjection, my team works on these docs and so I might be able
to comment up front. The Python 2.7 (only) and Go 1.9 (only) runtimes are
"first generation" App Engine runtimes which use the App Engine Task Queues
API which is internal to App Engine and not compatible with other products.
The other runtimes, including the newer versions of Python and Go and also
other supported languages such as Node, are "second generation" App Engine
runtimes and instead of using App Engine-specific APIs, they have access to
the Cloud-wide APIs such as Cloud Tasks and Cloud Pub/Sub which are what we
recommend going forward.

In the specific case of pull queues, we instead recommend using the Cloud
Pub/Sub API which provides much of the pull queue functionality separate
from Task Queues. However, if this doesn't serve your needs, please reply
to this email (or directly to me) with feedback as we're actively gathering
customer feedback about any use cases that aren't covered by the new APIs.



On Mon, Jul 15, 2019 at 1:17 PM 'Elliott (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Govind,
>
> To have your question addressed, please click the “Send Feedback” link at
> the bottom of this page
> ,
> then “Documentation feedback” and follow the steps to ask your question.
> The documentation team will look into this matter for you.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/031d9fff-3d72-47be-9152-80c225e0f92f%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJc%2Br%2Bpd_4t%3D2U-m1jWqXNgQyDZs0m0ybHPfmVH5yvHYA%40mail.gmail.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

We don't have a replacement for that functionality yet, but I'll record
that that's a missing link for people migrating. Thank you!

On Fri, Jun 14, 2019 at 3:02 PM Nicolas Grilly 
wrote:

> On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:
>>
>> If you don't mind me asking, what are the features of dev_appserver.py
>> that are still useful with the newer runtimes, which do not have App
>> Engine-specific APIs and client libraries that dev_appserver was originally
>> intended to mock and emulate?
>>
>
> dev_appserver.py seems still useful to emulate dispatch.yaml and static
> handlers locally. Is there an alternative?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJvgea0PLXyRvcXP%3DDg-Lhoo2VDUXiVfNKT%2BYMxR%2BBCBg%40mail.gmail.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

The recommended alternative is to use what is idiomatic for your framework
or other development process, as you would outside of Google Cloud. This is
now possible because we no longer require the use of App Engine-specific
APIs, handlers definitions, etc. However, dev_appserver.py did have some
features beyond emulating App Engine APIs and processing handlers that some
people have integrated into their workflows, so if this new approach
doesn't work well for you, please let us know where the pain points are.

On Fri, Jun 14, 2019 at 2:10 PM James Crowley 
wrote:

> If there are alternatives I'm missing this would be awesome? The feedback
> cycle is super slow when testing Google cloud specific code when it takes
> 30 seconds+ to update a running app (and that's ignoring the downsides of
> only being able to work online)
>
> Thanks
>
> J
>
> On Friday, 14 June 2019 01:32:52 UTC+2, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/23ab05d6-eb3b-45f2-8282-479f7c3f14ec%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLGEJAHFMnAAvcfkTNYfRQVa6DnqKCEb50R1PTxbuDKGA%40mail.gmail.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

We're aiming to build all of our new runtimes so that they don't require
dev_appserver.py, by making them support the same APIs and idiomatic local
development practices that one would use on any platform. If you don't mind
me asking, what are the features of dev_appserver.py that are still useful
with the newer runtimes, which do not have App Engine-specific APIs and
client libraries that dev_appserver was originally intended to mock and
emulate?

On Fri, Jun 14, 2019 at 9:31 AM 'Nicolas (Google Cloud Platform Support)'
via Google App Engine  wrote:

> Hi James,
>
>
>
> Thanks for opening this thread,
>
>
>
> To answer your question you are right the dev_appserver.py
> 
> is not supported with the PHP 7.2 and PHP 7.3 runtimes.
>
>
>
> To test your app locally you can download and install PHP 7.2 or PHP 7.3
> and set up a web server.
>
>
> Dev_appserver.py will still be available for PHP 5/7
> 
> and no deprecation is planned for the moment.
>
>
>
>
>
> On Thursday, June 13, 2019 at 7:32:52 PM UTC-4, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/478d514d-d1b4-46a4-9e91-9fb715cc7439%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJkJkRJJRqpMeCjB4LSY50oYS4TnB67TLqAgf6cbLQ9Ww%40mail.gmail.com.

[google-appengine] Python 3 NDB Datastore library alpha

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,

As part of our efforts to ensure App Engine Standard Python 2.7 users are
able to migrate to Python 3, we are developing an updated version of the
NDB Datastore client library that is compatible with Cloud Datastore and
Python 3.

I'm pleased to announce the new Python 3 NDB is in Alpha and is ready for
initial user testing. I'd appreciate it if anyone interested in migrating
NDB-using GAE Python 2.7 apps could take our new version for a spin and
send in their comments. The primary target platform is the GAE Python 3
runtime, but unlike the original version of NDB, this library does not rely
on App Engine specifics and should run anywhere.

The library can be installed with `pip install google-cloud-ndb` and the
source code can be found here: https://github.com/googleapis/python-ndb.
Please refer to MIGRATION_NOTES.md (
https://github.com/googleapis/python-ndb/blob/master/MIGRATION_NOTES.md)
for usage details; in particular, read the "Bootstrapping" section.

API documentation is published here:
https://googleapis.github.io/python-ndb/latest/ and the original
documentation for the Python 2.7 version is still available here:
https://cloud.google.com/appengine/docs/standard/python/ndb/ with more
detailed usage information, though not all of it will apply to the new
version.

This library is specifically intended to facilitate migration from GAE
Python 2.7 to any Python 3 platform, especially GAE Python 3. While any
Datastore user can download and use the NDB library, our recommendation for
new apps is still to use the Cloud Client Datastore library bundled with
the Google Cloud SDK.

Please send feedback or feature requests by opening an issue on our GitHub
repo, by responding to this email or by reaching out directly to me at
gorces...@google.com.

Due to differences in the programming environment between GAE Python 2.7
and our Python 3 runtime, we cannot be 100% compatible in all cases,
especially where there was unexpected or unclear behavior in the 2.7
library. However, we will make every effort to be compatible where possible
and document any differences while not. If you run into any incompatibility
or missing feature that is not explicitly called out in MIGRATION_NOTES.md,
please let us know. Also let us know if you run into an issue that is
called out in the migration notes but impacts you in a way we might not
have expected, or you have suggestion for a workaround or fix.

Finally, please keep in mind that this project is still in active
development and is not yet suitable for use in a production environment.

Thanks for your continued support of our platform. I am looking forward to
hearing from the community on this and upcoming efforts.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2Bj-T1RTKg1EYWddpWwk3wDsE4PcY2DHDBXr79O%3DP05JA%40mail.gmail.com.