Hello, Thanks for bringing this implementation to our attention.
As a best course of action, I would suggest that you submit a feature request ticket via the public issue tracker [1]. That way, this will generate more visibility for the App Engine team and they who be able to further evaluate the implementation. Let us know if you have any questions or concerns in regards to this process. [1] https://cloud.google.com/support/docs/issue-trackers#feature_requests On Sunday, February 14, 2021 at 11:11:33 AM UTC-5 [email protected] wrote: > It's also important to note that the original library was from somewhere > else that is long lost now, so I didn't write the original library > > On Sunday, February 14, 2021 at 7:10:12 PM UTC+3 Kaan wrote: > >> Hacked together this very ugly standalone Amazon SES library for the >> Python 2.7 / App Engine relics out there - it was such a chore and required >> so much trial and error that I almost was going to re-write the entire >> project on NodeJS / App Engine instead >> >> https://gist.github.com/kaansoral/b03881bd936d519543232e3573f9137d >> >> Amazon deprecates AWS3 signing for AWS4 this month, so this will allow >> you to just keep on using SES without diving deep into the rabbit hole >> >> And the obligatory remark about why GCP is making us suffer like this and >> promote other cloud services and so on >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/17c889f2-78dd-429a-846e-5ce60ced0ec4n%40googlegroups.com.
