Re: [google-appengine] ImportError: No module named django.core.handlers.wsgi

[Mak Ahmad]

ok I can run it now with command line

So the sys.path was pointing to gcloudsdk's django 1.5 folder which didn't 
even exist. So I copied it from my google app engine folder and it worked

cp -R /Users/USERNAME/Documents/google_appengine/lib/django-1.5 /Users/
USERNAME/gcloudsdk/google-cloud-sdk/platform/google_appengine/lib

 thanks all

On Monday, August 29, 2016 at 11:51:27 AM UTC-7, Adam (Cloud Platform 
Support) wrote:
>
> As I mentioned, this variable should not even be needed, so try removing 
> that line completely. If that doesn't work, something else is messing up 
> your sys.path, so please try dumping sys.path from your app handler to 
> see what's going on.
>
> On Sunday, August 28, 2016 at 6:51:56 PM UTC-4, Mak Ahmad wrote:
>>
>> I made that change in the bash file and re-ran the export and get this now
>>
>> USERNAME-macbookpro:Documents USERNAME$ export |grep PYTHON
>>
>> declare -x PYTHONPATH=
>> ":/Users/USERNAME/Documents/google_appengine:/Users/USERNAME/Documents/google_appengine/lib/django-1.5"
>>
>> my bash profile is now
>>
>>
>>
>> # The next line updates PATH for the Google Cloud SDK.   
>>
>>
>> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/path.bash.inc'
>>
>>
>>
>> # The next line enables shell command completion for gcloud. 
>>
>>
>> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/completion.bash.inc'
>>
>>
>>
>> export GAE="/Users/USERNAME/Documents/google_appengine"
>>
>> export PYTHONPATH="$GAE:$GAE/lib/django-1.5"
>>
>> #export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5" 
>>   
>>
>> export PATH=${PATH}:$GAE/lib/django-1.5/django/bin/
>>
>> running the server, I still get the import django error using command line
>>
>> On Sunday, August 28, 2016 at 10:59:11 AM UTC-7, Yunkai Zhou wrote:
>>>
>>> Hi Mak,
>>>
>>> Try modify
>>>
>>> export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5"
>>>
>>> to
>>>
>>> export PYTHONPATH="$GAE:$GAE/lib/django-1.5"
>>>
>>> I suspect $PYTHONPATH is empty string before that export line, which 
>>> creates a leading : after export.
>>>
>>> On Sunday, August 28, 2016, Mak Ahmad  wrote:
>>>
 Hi Adam,

 How do I remove them from the PYTHONPATH? Here's what I get when I do 
 emacs ~/.bash_profile











 # The next line updates PATH for the Google Cloud SDK. 
  

 source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/path.bash.inc'



 # The next line enables shell command completion for gcloud.   
  

 source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/completion.bash.inc'



 export GAE="/Users/USERNAME/Documents/google_appengine"

 export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5"

 export PATH=${PATH}:$GAE/lib/django-1.5/django/bin/



 Is this where it needs to be changed I don't even know where the 
 leading ':' syntax error came from 



 On Saturday, August 27, 2016 at 12:04:30 PM UTC-7, Adam (Cloud Platform 
 Support) wrote:
>
> It's not necessary to add any of the App Engine SDK paths to 
> PYTHONPATH for the development server to work. There's also a syntax 
> error (the leading ':'). I'd advise just not setting it at all in your 
> shell's config file.
>
> If that doesn't resolve the issue, you can try making a small handler 
> from the development server that just prints sys.path and share the 
> output of that. It will also help to confirm if *all* external 
> imports don't work and not just the Django import.
>
> On Tuesday, August 23, 2016 at 10:25:38 PM UTC-4, Mak Ahmad wrote:
>>
>> here it is Adam
>>
>> USERNAME-macbookpro:Documents USERNAME$ which python
>>
>> /usr/bin/python 
>>
>> USERNAME-macbookpro:Documents USERNAME$ python --version 
>>
>> Python 2.7.10 
>>
>> USERNAME-macbookpro:Documents USERNAME$ export|grep PYTHON 
>>
>> declare -x PYTHONPATH=
>> ":/Users/USERNAME/Documents/google_appengine:/Users/USERNAME/Documents/google_appengine/lib/django-1.5"
>>
>>
>> hope that helps
>>
>>
>>
>> On Tuesday, August 23, 2016 at 3:15:44 PM UTC-7, Adam (Cloud Platform 
>> Support) wrote:
>>>
>>> I'm glad you were able to get it to work with the launcher. If you 
>>> get ImportErrors only when starting from the terminal it's possible 
>>> your 
>>> Python interpreter is misconfigured. You might want to share the output 
>>> of 
>>> the following:
>>>
>>> Check which Python interpreter you're using
>>> $ which python
>>>
>>> Check your python version
>>> $ python --version
>>>
>>> Check any Python environment variables eg. PYTHON_PATH
>>> $ export | grep PYTHON
>>>
>>>
>>> On Monday, August 22, 2016 at 

[google-appengine] Re: AppEngine Go runtime for Mac OS X 64-bit

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

AMD64 is actually the standard used by both Intel and AMD, and is just 
another name for 'x86-64' or 'x64' . 
It's so named because AMD first developed the architecture which Intel 
later adopted. Rest assured, we would not release an SDK for a 
'darwin_amd64' architecture if it didn't exist! 

As for the reason it's crashing on your system, it's likely that you just 
have an older 32-bit version of Go installed. As of Go 1.5, 'darwin-amd64' 
is the only supported architecture . You can 
confirm your version and architecture by typing 'go version' from the 
command prompt.

Otherwise, if you have a very old 2008 or prior Mac with a 1st gen Core 
processor, your Mac is 32-bit only.

On Sunday, August 28, 2016 at 11:45:39 AM UTC-4, Dmitry Matyukhin wrote:
>
> I tried to use Go Runtime for AppEngine for Mac. Since, there is a 64-bit 
> version, I installed that one.
>
> However, whenever I tried to run anything, it was always crashing. For 
> example, this happens when I did "goapp get google.golang.org/appengine"
>
> # net
> fatal error: unexpected signal during runtime execution
> [signal 0xb code=0x1 addr=0x1161be989d12 pc=0xf0eb]
>
> runtime stack:
> runtime.throw(0x497380, 0x2a)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/panic.go:547
>  
> +0x90
> runtime.sigpanic()
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/sigpanic_unix.go:12
>  
> +0x5a
> runtime.unlock(0x988540)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/lock_sema.go:107
>  
> +0x14b
> runtime.(*mheap).alloc_m(0x988540, 0x1, 0x21, 0xec2ff0)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:492
>  
> +0x314
> runtime.(*mheap).alloc.func1()
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:502
>  
> +0x41
> runtime.systemstack(0x7fff5fbfe348)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:307
>  
> +0xab
> runtime.(*mheap).alloc(0x988540, 0x1, 0x121, 0xed8f)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mheap.go:503
>  
> +0x63
> runtime.(*mcentral).grow(0x98a680, 0x0)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:209
>  
> +0x93
> runtime.(*mcentral).cacheSpan(0x98a680, 0xec2ff0)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcentral.go:89
>  
> +0x47d
> runtime.(*mcache).refill(0xafa000, 0x21, 0xec2ff0)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/mcache.go:119
>  
> +0xcc
> runtime.mallocgc.func2()
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:642
>  
> +0x2b
> runtime.systemstack(0x979d00)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:291
>  
> +0x79
> runtime.mstart()
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/proc.go:1051
>
> goroutine 1 [running]:
> runtime.systemstack_switch()
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/asm_amd64.s:245
>  
> fp=0xc8241ed290 sp=0xc8241ed288
> runtime.mallocgc(0x500, 0x0, 0x3, 0xc825f0c400)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:643
>  
> +0x869 fp=0xc8241ed368 sp=0xc8241ed290
> runtime.rawmem(0x500, 0x200)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/malloc.go:809
>  
> +0x32 fp=0xc8241ed390 sp=0xc8241ed368
> runtime.growslice(0x3b2760, 0xc825f0c400, 0x400, 0x400, 0x401, 0x0, 0x0, 
> 0x0)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/runtime/slice.go:95
>  
> +0x233 fp=0xc8241ed400 sp=0xc8241ed390
> cmd/internal/obj.Symgrow(0xc8200b4000, 0xc8221d5b80, 0x401)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/cmd/internal/obj/data.go:50
>  
> +0x237 fp=0xc8241ed4c0 sp=0xc8241ed400
> cmd/internal/obj/x86.span6(0xc8200b4000, 0xc8221d5b80)
> 
> /private/var/folders/9y/ppk2fnqj5lscwqw_l6lhdrx8005bt1/T/appengine/go_appengine/goroot/src/cmd/internal/obj/x86/asm6.go:1962
>  
> +0x9b9 fp=0xc8241ed650 sp=0xc8241ed4c0
> cmd/internal/obj.Flushplist(0xc8200b4000)
> 
> 

[google-appengine] Re: [Newbie] How to create a REST based API backend in Python?

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

I would recommend reading all of the Endpoints documentation (which isn't a 
lot), starting with the overview 
, as it will 
answer all of these questions. Endpoints handles the conversion of models 
to messages for you, and communicates using JSON. You can generate client 
libraries automatically, or you can talk to your Endpoints back-end 
directly over HTTP.

If your question is how to create a REST API without using Endpoints or any 
library, you're essentially asking how to write your own REST framework 
which is probably outside the scope of a Google Groups post.

On Saturday, August 27, 2016 at 11:27:50 AM UTC-4, pratibha s wrote:
>
> Hi,
>
> I'm GAE newbie. I'm trying to implement a RESTful API for a python based 
> backend. I'm reading the docs and here is what I learnt. 
> 1. GAE recommends using cloud endpoints which originally uses protoRPC to 
> expose models via APIs. 
> 2. This means models need to be converted to RPC messages for 
> communicating with the API. 
> 3. Use a REST based API which will enable directly manipulating the model 
> entities via API.
>
> Here is my question, without using external third party libraries, how do 
> you create a REST based APIs? 
>
> Regards,
> Pratibha
>

-- 
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/a580094d-52c9-44a9-abc4-aea785f0aba5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google Cloud Storage browser - can't share files publicly

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

Yes, it's a known issue. For know the workaround as mentioned in the above 
link is to manually go to 'Edit permissions' and add the User 'allUsers' 
with Reader permission, or use the gsutil 
 command to 
set permissions.

On Monday, August 29, 2016 at 1:52:10 PM UTC-4, Matej Ramuta wrote:
>
> Someone found a nice hack for this problem: 
> https://code.google.com/p/google-cloud-sdk/issues/detail?id=1082 :)
>
> On Monday, August 29, 2016 at 3:06:15 PM UTC+2, Matej Ramuta wrote:
>>
>> Wonder if changing the html (adding in a checkbox) would help. The only 
>> catch would be to know the name attribute of the input element :)
>>
>> On Aug 29, 2016 12:10, "Леонтьев Пётр" wrote:
>>
>>> Tried to clear cache, refresh/change browser, create/change/delete user, 
>>> manage permissions - nothing seems to work.
>>>
>>> -- 
>>> 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/XDEvsuem8Hw/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, 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/c6c06de1-d4be-4e1f-98cf-adab01b49892%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/1dc51089-dc2e-488b-b4f5-eccef3781e09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Multiprocessing in python

['Jungho Ahn' via Google App Engine]

I'm using python:

runtime: python
runtime_config:
python_version: 2


On Mon, Aug 29, 2016 at 12:32 PM, 'Adam (Cloud Platform Support)' via
Google App Engine  wrote:

> Which Python runtime are you using? (the 'runtime
> '
> line in your app.yaml)
>
> On Saturday, August 27, 2016 at 7:36:31 PM UTC-4, Jungho Ahn wrote:
>>
>> On Aug 27, 2016 4:16 PM, "'Adam (Cloud Platform Support)' via Google App
>> Engine"  wrote:
>> >
>> > Multiple cores are not available to App Engine standard runtime
>> instances. If you need access to multiple cores on the same instance,
>> consider using the App Engine flexible runtime, which uses Compute Engine
>> as the underlying VM and allows you to configure the number of cores
>> available.
>> >
>>
>> Yes, but i can't use multiprocess in Python flexible appengine. When I
>> created a process, it was a fake process which is a thread like in
>> appengine.
>>
>> >
>> > On Wednesday, August 24, 2016 at 4:27:17 PM UTC-4, Jungho Ahn wrote:
>> >>
>> >> Hello,
>> >>
>> >> Is it allowed to use python multiprocessing in appengine?
>> >> I tried, but it looks like only one core is utilized.
>> >>
>> >> Thanks,
>> >
>> > --
>> > 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/to
>> pic/google-appengine/D6z_WoLsBH8/unsubscribe.
>> > To unsubscribe from this group and all its topics, 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/ms
>> gid/google-appengine/88dafadf-a328-423e-8ddc-7c4f585f88a9%
>> 40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/D6z_WoLsBH8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/2fd63c21-f33f-48a2-932d-
> bd7db89cb56c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jungho Ahn

-- 
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%2B_Q-HOQzTGBsiyndj-RKmPkFpm_n0VPdSC1Pj3wmpS-uGPZZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: REST DELETE API with request body

[Jason Collins]

The public issue tracker for this is 
here: https://code.google.com/p/googleappengine/issues/detail?id=601

Unfortunately, as per the RFC, you cannot supply a body with a DELETE 
request.

When I've hit this in the past, I've been lucky enough that the API 
provided also supported an equivalent POST endpoint (in my case I had to 
specify the query argument ?method=DELETE).


On Sunday, 28 August 2016 23:22:29 UTC-7, Vinod Kumar wrote:
>
> Hi,
>
> I am trying to delete multiple records through  REST DELETE API. For some 
> reason the request body is not reaching the API. I know that it is not 
> recommended to send a request body in REST DELETE. How can i achieve 
> deletion of multiple records?
>

-- 
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/12fd1cc4-e210-4aac-a1a7-cfe91d793c12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Multiprocessing in python

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

Which Python runtime are you using? (the 'runtime 
'
 
line in your app.yaml)

On Saturday, August 27, 2016 at 7:36:31 PM UTC-4, Jungho Ahn wrote:
>
> On Aug 27, 2016 4:16 PM, "'Adam (Cloud Platform Support)' via Google App 
> Engine"  wrote:
> >
> > Multiple cores are not available to App Engine standard runtime 
> instances. If you need access to multiple cores on the same instance, 
> consider using the App Engine flexible runtime, which uses Compute Engine 
> as the underlying VM and allows you to configure the number of cores 
> available.
> >
>
> Yes, but i can't use multiprocess in Python flexible appengine. When I 
> created a process, it was a fake process which is a thread like in 
> appengine.
>
> >
> > On Wednesday, August 24, 2016 at 4:27:17 PM UTC-4, Jungho Ahn wrote:
> >>
> >> Hello,
> >>
> >> Is it allowed to use python multiprocessing in appengine?
> >> I tried, but it looks like only one core is utilized.
> >>
> >> Thanks,
> >
> > -- 
> > 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/D6z_WoLsBH8/unsubscribe
> .
> > To unsubscribe from this group and all its topics, 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/88dafadf-a328-423e-8ddc-7c4f585f88a9%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/2fd63c21-f33f-48a2-932d-bd7db89cb56c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] ImportError: No module named django.core.handlers.wsgi

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

As I mentioned, this variable should not even be needed, so try removing 
that line completely. If that doesn't work, something else is messing up 
your sys.path, so please try dumping sys.path from your app handler to see 
what's going on.

On Sunday, August 28, 2016 at 6:51:56 PM UTC-4, Mak Ahmad wrote:
>
> I made that change in the bash file and re-ran the export and get this now
>
> USERNAME-macbookpro:Documents USERNAME$ export |grep PYTHON
>
> declare -x PYTHONPATH=
> ":/Users/USERNAME/Documents/google_appengine:/Users/USERNAME/Documents/google_appengine/lib/django-1.5"
>
> my bash profile is now
>
>
>
> # The next line updates PATH for the Google Cloud SDK. 
>  
>
> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/path.bash.inc'
>
>
>
> # The next line enables shell command completion for gcloud.   
>  
>
> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/completion.bash.inc'
>
>
>
> export GAE="/Users/USERNAME/Documents/google_appengine"
>
> export PYTHONPATH="$GAE:$GAE/lib/django-1.5"
>
> #export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5" 
>   
>
> export PATH=${PATH}:$GAE/lib/django-1.5/django/bin/
>
> running the server, I still get the import django error using command line
>
> On Sunday, August 28, 2016 at 10:59:11 AM UTC-7, Yunkai Zhou wrote:
>>
>> Hi Mak,
>>
>> Try modify
>>
>> export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5"
>>
>> to
>>
>> export PYTHONPATH="$GAE:$GAE/lib/django-1.5"
>>
>> I suspect $PYTHONPATH is empty string before that export line, which 
>> creates a leading : after export.
>>
>> On Sunday, August 28, 2016, Mak Ahmad  wrote:
>>
>>> Hi Adam,
>>>
>>> How do I remove them from the PYTHONPATH? Here's what I get when I do 
>>> emacs ~/.bash_profile
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> # The next line updates PATH for the Google Cloud SDK.   
>>>
>>>
>>> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/path.bash.inc'
>>>
>>>
>>>
>>> # The next line enables shell command completion for gcloud. 
>>>
>>>
>>> source '/Users/USERNAME/gcloudsdk/google-cloud-sdk/completion.bash.inc'
>>>
>>>
>>>
>>> export GAE="/Users/USERNAME/Documents/google_appengine"
>>>
>>> export PYTHONPATH="$PYTHONPATH:$GAE:$GAE/lib/django-1.5"
>>>
>>> export PATH=${PATH}:$GAE/lib/django-1.5/django/bin/
>>>
>>>
>>>
>>> Is this where it needs to be changed I don't even know where the leading 
>>> ':' syntax error came from 
>>>
>>>
>>>
>>> On Saturday, August 27, 2016 at 12:04:30 PM UTC-7, Adam (Cloud Platform 
>>> Support) wrote:

 It's not necessary to add any of the App Engine SDK paths to PYTHONPATH 
 for the development server to work. There's also a syntax error (the 
 leading ':'). I'd advise just not setting it at all in your shell's config 
 file.

 If that doesn't resolve the issue, you can try making a small handler 
 from the development server that just prints sys.path and share the 
 output of that. It will also help to confirm if *all* external imports 
 don't work and not just the Django import.

 On Tuesday, August 23, 2016 at 10:25:38 PM UTC-4, Mak Ahmad wrote:
>
> here it is Adam
>
> USERNAME-macbookpro:Documents USERNAME$ which python
>
> /usr/bin/python 
>
> USERNAME-macbookpro:Documents USERNAME$ python --version 
>
> Python 2.7.10 
>
> USERNAME-macbookpro:Documents USERNAME$ export|grep PYTHON 
>
> declare -x PYTHONPATH=
> ":/Users/USERNAME/Documents/google_appengine:/Users/USERNAME/Documents/google_appengine/lib/django-1.5"
>
>
> hope that helps
>
>
>
> On Tuesday, August 23, 2016 at 3:15:44 PM UTC-7, Adam (Cloud Platform 
> Support) wrote:
>>
>> I'm glad you were able to get it to work with the launcher. If you 
>> get ImportErrors only when starting from the terminal it's possible your 
>> Python interpreter is misconfigured. You might want to share the output 
>> of 
>> the following:
>>
>> Check which Python interpreter you're using
>> $ which python
>>
>> Check your python version
>> $ python --version
>>
>> Check any Python environment variables eg. PYTHON_PATH
>> $ export | grep PYTHON
>>
>>
>> On Monday, August 22, 2016 at 8:09:45 PM UTC-4, Mak Ahmad wrote:
>>>
>>> I tried a few things and also tried
>>>
>>> http://howto.pui.ch/post/39245389801/tutorial-django-on-appengine-using-google-cloud
>>>
>>> with no luck.
>>>
>>> So then I used the "Google App Engine Launcher" and added the 
>>> existing application there and hit start and it worked. For some reason 
>>> starting the application in a terminal using  "dev_appserver.py " 
>>> doesn't work but with the GUI it does
>>>
>>> On Friday, August 19, 2016 at 3:22:43 PM UTC-7, Adam (Cloud Platform 
>>> Support) 

Re: [google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Matej Ramuta]

Someone found a nice hack for this 
problem: https://code.google.com/p/google-cloud-sdk/issues/detail?id=1082 :)

On Monday, August 29, 2016 at 3:06:15 PM UTC+2, Matej Ramuta wrote:
>
> Wonder if changing the html (adding in a checkbox) would help. The only 
> catch would be to know the name attribute of the input element :)
>
> On Aug 29, 2016 12:10, "Леонтьев Пётр"  wrote:
>
>> Tried to clear cache, refresh/change browser, create/change/delete user, 
>> manage permissions - nothing seems to work.
>>
>> -- 
>> 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/XDEvsuem8Hw/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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/c6c06de1-d4be-4e1f-98cf-adab01b49892%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/077cb909-5a1a-4b28-9df0-78aa1ced4257%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] I can't open google.com on any browser.

[Liu Leo]

Hi everyone, I have two desktop, I could open google.com on a Dell desktop. 
But i can not open google.com on the desktop I build by myself. This 
happened recently I moved from Canada to California. I checked IE settings, 
and cache, either works good. I do not know if the problem is with the 
router ( COX cisco), if it does, I should not open google.com on my Dell 
desktop. 

-- 
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/8922c2ec-f0b0-4756-9be6-d56e7af39b93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: loading_request=0

[Deepak Singh]

Hi Nick,

Please find the attached graphs that will explain  the latency issues.

Regards
Tech team
On Aug 11, 2016 12:15 AM, "Deepak Singh"  wrote:

> Hi Nick,
>
> I will soon update you as i am currently out of station.
>
> On Tue, Aug 9, 2016 at 8:20 PM, 'Nick (Cloud Platform Support)' via Google
> App Engine  wrote:
>
>> Hey Deepak,
>>
>> Any update? I'm here and happy to assist.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Wednesday, August 3, 2016 at 12:43:33 PM UTC-4, Deepak Singh wrote:
>>>
>>> Sorry, missed to write the data
>>>
>>> Average request latency: 127.05
>>>
>>> CPU: 8.996
>>>
>>> No data for loading latency
>>>
>>> On Wed, Aug 3, 2016 at 10:08 PM, Deepak Singh 
>>> wrote:
>>>
 Hi Nick,

 Thanks for your detailed response.
 Based on your response, i guess that none of the data seems suspicious
 in our logs. Here is a log snippet
 ms=214 cpu_ms=0 cpm_usd=0.2771493 loading_request=0 instance=-
 app_engine_release=1.9.42 trace_id=c0ed6d9452c7fa778840af791c4a291d

 However look at the below graphs where latency shows the data and cpu
 graph shows the enough instance. But still we have user latency.

 Google page speed test indicates server response time as close to 0.5
 sec which is quite high.





 CPU
 % CPU
 3 Aug, 12:003 Aug, 15:003 Aug, 18:003 Aug, 22:025101520

 Latency
 Milliseconds
 3 Aug, 12:003 Aug, 15:003 Aug, 18:003 Aug,
 21:5920,00040,00060,00080,000100,000120,000
  Average request latency:

 On Wed, Aug 3, 2016 at 12:58 AM, 'Nick (Cloud Platform Support)' via
 Google App Engine  wrote:

> Hey Deepak,
>
> This means this was not the first request to the instance. This means
> that most of your requests are being handled by instances which already
> existed when the request was received by the App Engine front-end load
> balancer.
>
> If you are still seeing latency, this could be caused by the instances
> being overloaded and the requests waiting in the pending queue in front of
> the instance (you can read about pending queues
> 
> and scaling parameters in the app.yaml documentation
> 
> (if using Java, see the appengine-web.xml documentation
> 
> which is analogous)). In that case, you'll see another field, "pending_ms"
> in the log line. You can solve this type of latency by changing the 
> scaling
> settings (see the docs).
>
> If you don't see very high values for "pending_ms", check whether
> "cpu_ms" is comparable to the total request latency, as this could mean
> that your instance is taking a large amount of time to process the 
> request.
>
> If the "ms" field is high but the "cpu_ms" is not high, this could
> mean that a remote API call made during handling the request takes a long
> time to complete while the instance waits for it to return before sending
> the response.
>
> Finally, if the "ms" field is not high compared to what the client
> observes, it's possible that the extra time is added during network
> transfer to and from the App Engine infrastructure and your instance. This
> could be solved by improving the network the client is on (not always a
> possibility) or locating the app closer to them (create an EU application
> if clients are in Europe).
>
> You can read more about request log fields in the documentation
> 
> .
>
> I hope this short guide is helpful in determining the cause of the
> request latency. If you have any further questions, let me know and I'll 
> be
> happy to assist!
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
>
> On Friday, July 29, 2016 at 12:01:29 PM UTC-4, Deepak Singh wrote:
>>
>> I see almost all of my request logs has loading_request=0
>>
>> We know that this is only present if the request causes the instance
>> to be started, so what should i understand based on this? our app faces
>> high latency most of the time.
>>
>> Java, flexible env based app.
>>
>> --
>> Tech
>>
> --
> 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, 

Re: [google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Matej Ramuta]

Wonder if changing the html (adding in a checkbox) would help. The only
catch would be to know the name attribute of the input element :)

On Aug 29, 2016 12:10, "Леонтьев Пётр"  wrote:

> Tried to clear cache, refresh/change browser, create/change/delete user,
> manage permissions - nothing seems to work.
>
> --
> 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/XDEvsuem8Hw/unsubscribe.
> To unsubscribe from this group and all its topics, 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/c6c06de1-d4be-4e1f-98cf-
> adab01b49892%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/CAM6S3HR1vT%2Bo6sgmJynEuUgQWGtLVtUMpPYOa81z_YNLHx3mgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Леонтьев Пётр]

Tried to clear cache, refresh/change browser, create/change/delete user, 
manage permissions - nothing seems to work.

-- 
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/c6c06de1-d4be-4e1f-98cf-adab01b49892%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Леонтьев Пётр]

Sorry to write this in different messages but need to say that gsutil works 
i.e. one can upload and share files publicly.

суббота, 27 августа 2016 г., 11:46:12 UTC+3 пользователь Matej Ramuta 
написал:
>
> Since yesterday I'm experiencing a bug on Google Cloud Storage browser. I 
> wanted to add some new images to it and make them public, but can't do that 
> anymore (see the image below or attachment). 
>
>- There's *no checkboxes* in the "Share publicly" column anymore.
>- I also tried *selecting an image* (Name column) and then *clicking 
>on "Share publicly"* button - but *nothing happens*.
>
> The *old images*, which were made public before the bug all *work ok*. *New 
> images* show *"Access denied"* XML when clicking on the *public* link.
>
> Does anyone know where the problem is? It's very weird...
>
>
> 
>
>

-- 
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/fe58d355-63ca-4a60-9a1a-3b22102ad5d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Леонтьев Пётр]

Seems like backend is broken - no checkboxes for newly uploaded files.

-- 
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/d8120215-51af-46b6-bd4b-6133e23a4701%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Cloud Storage browser - can't share files publicly

[Леонтьев Пётр]

We experience the same problem. Uploading is successful but can't share 
files publicly.

суббота, 27 августа 2016 г., 11:46:12 UTC+3 пользователь Matej Ramuta 
написал:
>
> Since yesterday I'm experiencing a bug on Google Cloud Storage browser. I 
> wanted to add some new images to it and make them public, but can't do that 
> anymore (see the image below or attachment). 
>
>- There's *no checkboxes* in the "Share publicly" column anymore.
>- I also tried *selecting an image* (Name column) and then *clicking 
>on "Share publicly"* button - but *nothing happens*.
>
> The *old images*, which were made public before the bug all *work ok*. *New 
> images* show *"Access denied"* XML when clicking on the *public* link.
>
> Does anyone know where the problem is? It's very weird...
>
>
> 
>
>

-- 
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/303f52c5-5f02-462e-8fd4-11ded1fa2c30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] URLFetchService getting timeouts

[Daniel Florey]

Hi,
since ~10 days we are getting a lot of "hanging" requests when using 
URLFetchService to upload files to our own servers.
It used to work just fine for the past years...
We can upload to our servers manually from our end without any issues, so 
it looks like an App Engine issue to me.
Anybody else affected?

Regards,
Daniel


10:07:11.294com.floreysoft.ultradox.server.adapter.TemplateAdapter 
transform: Template has been zipped 
10:07:11.294com.floreysoft.ultradox.server.adapter.TemplateAdapter convert: 
Starting upload of document (length=3534 bytes) to Ultradox engine with 
IP=85.214.114.14 
10:08:06.789com.floreysoft.ultradox.server.adapter.TemplateAdapter convert: 
Failed to retrieve document from Ultradox engine. Retry 1... 
com.google.apphosting.api.ApiProxy$CancelledException: The API call 
urlfetch.Fetch() was cancelled because the overall HTTP request deadline 
was reached. at 
com.google.apphosting.runtime.ApiProxyImpl.doSyncCall(ApiProxyImpl.java:275) 
at 
com.google.apphosting.runtime.ApiProxyImpl.access$000(ApiProxyImpl.java:73) 
at com.google.apphosting.runtime.ApiProxyImpl$1.run(ApiProxyImpl.java:215) 
at com.google.apphosting.runtime.ApiProxyImpl$1.run(ApiProxyImpl.java:212) 
at java.security.AccessController.doPrivileged(Native Method) at 
com.google.apphosting.runtime.ApiProxyImpl.makeSyncCall(ApiProxyImpl.java:211) 
at 
com.google.apphosting.runtime.ApiProxyImpl.makeSyncCall(ApiProxyImpl.java:73) 
at com.google.apphosting.api.ApiProxy.makeSyncCall(ApiProxy.java:122) at 
com.google.appengine.api.urlfetch.URLFetchServiceImpl.fetch(URLFetchServiceImpl.java:40)
 
at 
com.google.apphosting.utils.security.urlfetch.URLFetchServiceStreamHandler$Connection.fetchResponse(URLFetchServiceStreamHandler.java:543)
 
at 
com.google.apphosting.utils.security.urlfetch.URLFetchServiceStreamHandler$Connection.getInputStream(URLFetchServiceStreamHandler.java:422)
 
at 
com.google.apphosting.utils.security.urlfetch.URLFetchServiceStreamHandler$Connection.getResponseCode(URLFetchServiceStreamHandler.java:275)
 
at com.floreysoft.ultradox.server.adapter.TemplateAdapter.convert(
TemplateAdapter.java:1108 

)

-- 
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/60443f00-252b-4dd0-a589-d1aca71cd618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Implementing a personalized feed on Google App Engine

[Barada Sahu]

Thanks Kaan, Nick,

Eventually the solution I have implemented is akin to Kaan's in the sense 
that there is event driven feed generation for users. 

However since there are a bunch of users I cannot use a tag based solution 
as I would have to keep writing pretty often to the same table in Datastore 
(assuming a tag specific to each user). Instead I make a copy of the data 
element and attach it to the user's feed table. This makes the feed table 
grow pretty large as I have a bunch of copies of the same item across 
multiple feed models for users. It's a tradeoff between writing to the 
content table (frequently) vs user-feed table (less frequently). 

With the NDB library am using to access Datastore so it's already cached. 
The feed generation task although times out quite often on the AppEngine. I 
use auto-scaling and suspect this is the one causing issues, should 
possibly go onto a more managed service environment. 

More importantly I wanted to have a discussion on using Datastore as a 
storage engine and the data-model for writing a personalized feed and 
possible read-write impact of storing the feeds on the datastore. As it is 
a personalized feed am assuming there is a feed (model) per each user. How 
do I structure the associations of content-user in the feed model?

~ B

On Tuesday, May 10, 2016 at 1:19:12 AM UTC+5:30, Nick (Cloud Platform 
Support) wrote:
>
> Yep, Kaan's idea is very good. Pre-calculating the results and 
> periodically updating them is a great method, but knowing how to avoid 
> stale results, that is, knowing when to run the next dynamic query, is a 
> fine art to make sure users' experience is "live". 
>
> On Monday, May 9, 2016 at 3:13:36 PM UTC-4, Kaan Soral wrote:
>>
>> "personalized content" is complex regardless of GAE
>>
>> I have chronological + geo feeds, for each event, an entity is written 
>> for each person
>>
>> Then, that person fetches those entities while digesting the feed
>>
>> IMO, whatever you do, you have to pre-process things with GAE, as the 
>> on-request capacity is pretty low, it's not logical to dynamically generate 
>> a feed in a timely manner 
>>
>

-- 
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/1a8b0cdb-c553-4843-968b-2c018ff4e6bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] REST DELETE API with request body

[Vinod Kumar]

Hi,

I am trying to delete multiple records through  REST DELETE API. For some 
reason the request body is not reaching the API. I know that it is not 
recommended to send a request body in REST DELETE. How can i achieve 
deletion of multiple records?

-- 
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/95fc47f6-f4db-4e47-a532-66aca284854e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.