Hi Vitaly,
In addition to sending email, SendGrid can receive email or make sense of
the email you’ve already sent using webhooks. You may check related detail
on the "Sending Emails with SendGrid" documentation page
Hi. George
> Is there a special reason you can't re-program your app? Do you absolutely
> need to use GAE Mail service? The Mail service is not available in Python
> 3. You need to use a third-party mail provider such as SendGrid, Mailgun,
> or Mailjet to send email. All of these services
Hello Vitaly,
Is there a special reason you can't re-program your app? Do you absolutely
need to use GAE Mail service? The Mail service is not available in Python
3. You need to use a third-party mail provider such as SendGrid, Mailgun,
or Mailjet to send email. All of these services offer
Hi, George
require effort to re-program your app in an alternative manner.
>
For example, I can't re-program my app, that receives emails, using GAE
Mail service.
Also, most of suggestions in this document
(https://cloud.google.com/appengine/docs/standard/python3/python-differences)
offers
Someone wrote a wrapper for the cloud datastore API -
https://github.com/Bogdanp/anom-py. I haven't used it myself so can't
comment.
On Wednesday, January 9, 2019 at 12:31:46 PM UTC-8, Blaine Garrett wrote:
>
> I asked this in a different thread, but I wonder if anyone has tried to
> port the
I asked this in a different thread, but I wonder if anyone has tried to
port the ndb package as a standalone python 3 package.
Thus far, in my experiments, once I got the datastore emulator running
locally, converting the consumption of the datastore apis from ndb to
native objects has been the
Google has a policy of a one year deprecation policy for any GA runtime.
Given that nothing has been announced yet, please know that your
application will continue running for at least a year and that will be
the *minimum
*period for you to need to do anything.
I apologize on being very brief
its not the incompatibility of python (language/runtime), its missing
services with regard to GAE Standard 2.7 and GAE Standard 3.0. (memcache,
NDB, Search, Images, Users, webapp2, etc). Are these going to be duplicated
in GAE3? and if so, will existing data and model definitions in the 2.7
You are perfectly right, NP. Python 3 is made incompatible with 2, and
Python 3 does not support quite a few features, and will require effort to
re-program your app in an alternative manner. I was simply saying that
often the effort is not enormous, and becomes worthwhile on the longer
term.
Hi,
You said - *The effort involved is not necessary enormous in each case, in
a lot of cases this might take minutes.*
I beg to differ. There are a significant number of things which are not
supported in Python 3 and will require effort to find/deploy alternatives.
These include ndb ORM,
The mentioned date is the end of support. Already deployed apps are not
directly affected on an immediate time frame. On a longer term
though, you'll have to migrate your code to Python 3 or delete it. The
effort involved is not necessary enormous in each case, in a lot of cases
this might
Yes, it is important
Please send us google oficial clarifications.
--
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 - please provide a roadmap for GAE 2.7 standard, what will happen to
these apps?
will they be required to upgrade to the python 3.0 (2nd generation
runtimes)?
if so, can you address the significant differences listed here:
13 matches
Mail list logo
