I'm working with Codenvy writing a Google Appengine app, and I have found it to be INSANELY difficult to debug. If there's a syntax error I have to find it manually as the web page that loads when testing give me and error:500. Also, I often want to print but Codenvy doesn't support printing for python (that or I don't understand the correct method). Has anyone else experienced this and able to help? Perhaps developing in the cloud isn't as easy as I was hoping...
Asked
Active
Viewed 428 times
2
-
I think you are always going to loose some capability when not developing locally, your looking at a very immature toolset. – Tim Hoffman Aug 03 '13 at 03:27
-
This is true, but I'm also looking for pretty basic features... hopefully someone will have a solution, even if it's a wonky workaround. – jtsmith1287 Aug 03 '13 at 05:04
-
Printing generally won't work in appengine at all, you need to use logging. – Tim Hoffman Aug 03 '13 at 05:12
-
1Reading docs for code envy they only have debug support with java. This only leaves logging and inspecting the appengine logs. To be honest I would move your dev locally if your using python. – Tim Hoffman Aug 03 '13 at 05:18
-
@TimHoffman I use the collaboration functions in Codenvy, so moving to local IDE doesn't really help. I already have the IDE set up locally. Working on a project with a friend. I've tried the logging bug and it doesn't seem to be working. Ugh... lame. – jtsmith1287 Aug 03 '13 at 22:09
2 Answers
1
That's the answer. Codenvy just isn't ready yet for real use. Cloud9 IDE is fully functional. All my hopes and desires came true with this site.

jtsmith1287
- 1,110
- 2
- 13
- 24
1
I discovered that if you go to the Google App Developper Console, there is a menu on the left. Click on App Engine, then click on Logs. There you can see the internal server error (error 500) log, which pretty much tell you what went wrong.

Wildhorn
- 926
- 1
- 11
- 30