Re: [google-appengine] An update on webapp2

['Jon Parrott' via Google App Engine]

Karl, first and foremost: thanks for being the first person to contribute.


   1. Yes, I just missed the makefile when I was cleaning things up. I'll 
   remove that and update contributing.md to document how to run tests. In the 
   meantime, you can checkout the travis config file. Mostly, you just need to 
   install nox-automation and run nox -s tests. Travis ran for your PR and it 
   passed 
   .
   2. Enabling the CLA bot is standard procedure, and the OSS lawyer that 
   assisted me in moving over this project did not indicate that it should be 
   passed over. I am not lawyer, however, from what I understand t the CLA 
   does not remove any of your rights as a the author, it just grants the 
   project rights to your contribution (this seems to be pretty clearly stated 
   at the beginning of the CLA itself). If concerns over the CLA cause you to 
   not want to contribute further, I'll be happy to get you in contact our 
   open source programs office so that we can potentially address your 
   concerns.


On Sunday, April 10, 2016 at 7:49:07 PM UTC-7, Karl MacMillan wrote:
>
>
> On Apr 8, 2016, at 4:58 PM, 'Jon Parrott' via Google App Engine <
> google-a...@googlegroups.com > wrote:
>
> In a previous thread 
> , 
> several of you pointed out that webapp2 was abandoned and some of you 
> expressed interesting in helping maintain the project.
>
>
> Jon,
>
> Thanks for stepping up and making this happen. I’ve submitted a pull 
> request for the bug that I mentioned in that thread.
>
> Two things:
>
> 1) Is all of the test infrastructure checked in? I ask because the 
> Makefile (and the test target) are referencing a non-existent run_tests.py 
> in the root of the project. I also didn’t see any documentation on how to 
> run the tests, especially the ones with GAE dependencies.
>
> 2) Is it intentional that a CLA is being required to submit patches? I’m 
> not a CLA fan in general, but I understand that they may make sense in some 
> contexts. However, in this case it seems unfortunate and potentially 
> pointless to take a community project, pull it in as a Google project, and 
> then require a CLA. It’s not like you have the copyright grant for all of 
> the previous work so that requiring the CLA for new patches actually gets 
> you any sort of licensing freedom or full patent protection. If you really 
> want to go with this approach I’ll sign the CLA for this trivial patch, but 
> it will likely discourage me from any other contribution. (I hate to keep 
> complaining since you’ve done so much to move this forward - it’s just that 
> this seems like a really strange approach to take).
>
> Thanks - Karl
>
> I'm happy to provide an update. The original author has allowed the Google 
> Cloud Platform Developer Relations team to assume ownership of webapp2. 
> We've moved the project to github and we're ready to accept pull requests.
>
>- webapp2 now lives at GoogleCloudPlatform/webapp2 
>.
>- Tests are running on travis 
> and code coverage 
>reporting 
>.
>- The documentation is now published to readthedocs 
>.
>- The official website will soon be updated to redirect to readthedocs.
>
> We could really use the community's help to:
>
>- Test it! We cleaned up a bit of stuff and we want to make sure that 
>everything still works as expected.
>- Check the new documentation 
> for accuracy and report 
>any content errors or bad links.
>- Triage the issues 
>
> 
>  
>that were transferred over from the original project. If you want to just 
>review them and comment whether or not they are still relevant, that would 
>be super helpful.
>- Fix issues. :)
>
> We'll soon release version 3.0.0 to PyPI. This is to mark the ownership 
> transition. We will look into updating the version included with Google App 
> Engine.
>
> -- 
> 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-appengi...@googlegroups.com .
> To post to this group, send email to google-a...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/9a193edb-363d-4ce9-b64f-b0b818f5cd14%40googlegroups.com
>  
> 

Re: [google-appengine] An update on webapp2

[Karl MacMillan]

> On Apr 8, 2016, at 4:58 PM, 'Jon Parrott' via Google App Engine 
>  wrote:
> 
> In a previous thread 
> , 
> several of you pointed out that webapp2 was abandoned and some of you 
> expressed interesting in helping maintain the project.
> 

Jon,

Thanks for stepping up and making this happen. I’ve submitted a pull request 
for the bug that I mentioned in that thread.

Two things:

1) Is all of the test infrastructure checked in? I ask because the Makefile 
(and the test target) are referencing a non-existent run_tests.py in the root 
of the project. I also didn’t see any documentation on how to run the tests, 
especially the ones with GAE dependencies.

2) Is it intentional that a CLA is being required to submit patches? I’m not a 
CLA fan in general, but I understand that they may make sense in some contexts. 
However, in this case it seems unfortunate and potentially pointless to take a 
community project, pull it in as a Google project, and then require a CLA. It’s 
not like you have the copyright grant for all of the previous work so that 
requiring the CLA for new patches actually gets you any sort of licensing 
freedom or full patent protection. If you really want to go with this approach 
I’ll sign the CLA for this trivial patch, but it will likely discourage me from 
any other contribution. (I hate to keep complaining since you’ve done so much 
to move this forward - it’s just that this seems like a really strange approach 
to take).

Thanks - Karl

> I'm happy to provide an update. The original author has allowed the Google 
> Cloud Platform Developer Relations team to assume ownership of webapp2. We've 
> moved the project to github and we're ready to accept pull requests.
> webapp2 now lives at GoogleCloudPlatform/webapp2 
> .
> Tests are running on travis 
>  and code coverage 
> reporting 
> .
> The documentation is now published to readthedocs 
> .
> The official website will soon be updated to redirect to readthedocs.
> We could really use the community's help to:
> Test it! We cleaned up a bit of stuff and we want to make sure that 
> everything still works as expected.
> Check the new documentation  for 
> accuracy and report any content errors or bad links.
> Triage the issues 
> 
>  that were transferred over from the original project. If you want to just 
> review them and comment whether or not they are still relevant, that would be 
> super helpful.
> Fix issues. :)
> We'll soon release version 3.0.0 to PyPI. This is to mark the ownership 
> transition. We will look into updating the version included with Google App 
> Engine.
> 
> -- 
> 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 post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/9a193edb-363d-4ce9-b64f-b0b818f5cd14%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1FBD6FE8-128F-4723-9C25-478584BF74AF%40strajillion.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cannot send mail

[Keith Chan]

Using the following java code:

Properties props = new Properties();
Session session = Session.getDefaultInstance(props, null);
Message msg = new MimeMessage(session);
msg.setFrom(new InternetAddress(FROM_EMAIL, "Sender"));
msg.addRecipient(Message.RecipientType.TO, new InternetAddress(email, 
name));
msg.setSubject(title);
msg.setText(msgBody);
Transport.send(msg);

If the msgBody contains a URL like
MyApplication.appspot.com
the message won't be received by the recipient, but system has no error log
If I change the content to:
MyApplication.appspot._com
then everything works fine

This happens on both Java and Python, seems the email server has a filter 
not sending message with valid URL.


-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8b03b7e2-8344-4c1b-8ea8-7e3633d15f76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Is there a list of all possible HTTP_X_APPENGINE_CITY/REGION/COUNTRY combos?

['Adam (Cloud Platform Support)' via Google App Engine]

If you check the documentation 
, it mentions 
that X-AppEngine-Country uses the ISO 3166-1 alpha-2  
country code, 
and X-AppEngine-Region uses the ISO-3166-2 
 code. There is no standard 
canonical list of cities for X-AppEngine-City, but the closest thing may be 
the United Nations UN/LOCODE Code List 
.

On Friday, April 8, 2016 at 8:56:45 PM UTC-4, Bret Lowery wrote:
>
> Is there a publically-available list or db available of all possible 
> HTTP_X_APPENGINE_CITY, HTTP_X_APPENGINE_REGION, and 
> HTTP_X_APPENGINE_COUNTRY combinations that can be generated by any web 
> request to App Engine?
>
>
>

-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/63fdce19-5c8e-42b3-b492-34411cf46b49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] GAE instance prices?

[George-Cristian Bîrzan]

I doubt however that they will go up 8 fold, which seems to be the gap
currently
On 10 Apr 2016 10:07 pm, "Susan Lin"  wrote:

> Hi Jeff, yes you are correct they currently use these resources, but
> according to Google from https://cloud.google.com/appengine/pricing these
> prices will increase (which I assume is to the standard GAE prices) once
> flex environment becomes GA.
>
> "Instances within the flexible environment are charged the cost of the
> underlying Google Compute Engine Virtual Machines
> . This is Beta-only pricing and
> will increase once the flexible environment is GA."
>
> So these lower prices seem to be only temporary.
>
> On Saturday, April 9, 2016 at 2:25:28 PM UTC-7, Jeff Schnitzer wrote:
>>
>> “nearly exact” I meant to say. EB and Flexible runtimes are both mapped
>> to a whole hypervisor VM.
>>
>> Jeff
>>
>> On Sat, Apr 9, 2016 at 2:24 PM, Jeff Schnitzer 
>> wrote:
>>
>>> If you want a nearly close comparison to ElasticBeanstalk, use a Managed
>>> VM (or “Flexible Runtime” I think they’re being called now). They are
>>> currently billed at the same rate as the underlying Compute Engine instance.
>>>
>>> Jeff
>>>
>>> On Fri, Apr 8, 2016 at 11:00 AM, Susan Lin  wrote:
>>>
 I tested out Google App Engine 4 years ago and am coming back now to
 see if it is a possibility for another project I will be working on. I see
 the pricing for instances are still the same as they were 4 years ago:

 This table summarizes the CPU, memory, and hourly billing rate of the
 various instance classes.
 Instance ClassMemory LimitCPU LimitCost per Hour per Instance




 F1 128 MB 600 Mhz $0.05
 F2 256 MB 1.2 Ghz $0.10
 F4 512 MB 2.4 Ghz $0.20
 F4_1G 1024 MB 2.4 Ghz $0.30
 When compared to Amazon's PaaS ElasticBeanstalk a 1 cpu 1GB instance
 costs $0.013 an hour which is almost 30 times cheaper than Google App
 Engine front end instances. I understand they offer different services, but
 as far as front end instances it is hard to see why in 2016 (Moore's Law) a
 1gb GAE instance is still so expensive. Does Google have any plans to lower
 the costs of these instances in the very near future?

 --
 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-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
 Visit this group at https://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/9020a9f4-886b-4841-9de0-314c14c0ffee%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>> --
> 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 post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/4a50cbef-7fc0-49f2-a275-67feebdcd990%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2B3w0iU%3DTApuuhqf8e5jdnBbEGY6WsyV%3DhQg5MOUkNXQhyz6JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: An update on webapp2

[pdknsk]

This is good news. The new App Engine docs seem to focus on Flask now, but 
webapp2 still works well, less a few minor annoyances.

https://cloud.google.com/appengine/docs/flexible/python/

> Although this sample uses Flask, you can use any framework that satisfies 
the requirements above. Alternative frameworks include Django, Pyramid, 
Bottle, web.py, Tornado, and more.

I was surprised that webapp2 isn't even mentioned.

-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/bcf0d555-6b89-4c43-9339-d78d936092e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] GAE instance prices?

[Susan Lin]

Hi Jeff, yes you are correct they currently use these resources, but 
according to Google from https://cloud.google.com/appengine/pricing these 
prices will increase (which I assume is to the standard GAE prices) once 
flex environment becomes GA.

"Instances within the flexible environment are charged the cost of the 
underlying Google Compute Engine Virtual Machines 
. This is Beta-only pricing and 
will increase once the flexible environment is GA."

So these lower prices seem to be only temporary.

On Saturday, April 9, 2016 at 2:25:28 PM UTC-7, Jeff Schnitzer wrote:
>
> “nearly exact” I meant to say. EB and Flexible runtimes are both mapped to 
> a whole hypervisor VM.
>
> Jeff
>
> On Sat, Apr 9, 2016 at 2:24 PM, Jeff Schnitzer  > wrote:
>
>> If you want a nearly close comparison to ElasticBeanstalk, use a Managed 
>> VM (or “Flexible Runtime” I think they’re being called now). They are 
>> currently billed at the same rate as the underlying Compute Engine instance.
>>
>> Jeff
>>
>> On Fri, Apr 8, 2016 at 11:00 AM, Susan Lin > > wrote:
>>
>>> I tested out Google App Engine 4 years ago and am coming back now to see 
>>> if it is a possibility for another project I will be working on. I see the 
>>> pricing for instances are still the same as they were 4 years ago:
>>>
>>> This table summarizes the CPU, memory, and hourly billing rate of the 
>>> various instance classes.
>>> Instance ClassMemory LimitCPU LimitCost per Hour per Instance
>>>
>>>
>>>
>>>
>>> F1 128 MB 600 Mhz $0.05
>>> F2 256 MB 1.2 Ghz $0.10
>>> F4 512 MB 2.4 Ghz $0.20
>>> F4_1G 1024 MB 2.4 Ghz $0.30
>>> When compared to Amazon's PaaS ElasticBeanstalk a 1 cpu 1GB instance 
>>> costs $0.013 an hour which is almost 30 times cheaper than Google App 
>>> Engine front end instances. I understand they offer different services, but 
>>> as far as front end instances it is hard to see why in 2016 (Moore's Law) a 
>>> 1gb GAE instance is still so expensive. Does Google have any plans to lower 
>>> the costs of these instances in the very near future?
>>>
>>> -- 
>>> 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-appengi...@googlegroups.com .
>>> To post to this group, send email to google-a...@googlegroups.com 
>>> .
>>> Visit this group at https://groups.google.com/group/google-appengine.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/9020a9f4-886b-4841-9de0-314c14c0ffee%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
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 post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4a50cbef-7fc0-49f2-a275-67feebdcd990%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.