Should I wait on upgrading then? I use pdb.set_trace() pretty heavily.
On Saturday, March 23, 2013 2:45:57 PM UTC-7, D X wrote:
I used to use pdb.set_trace() because the debugger was so slow.
It got monkeypatched to work in one of the more recent builds, but now
that there's multiple processes running and stdout is closed, it doesn't
work anymore.
This is a huge problem. Part of the reason I like using App Engine was
that it was easy to develop on. Not so much when the only way you can
debug is via a multithreaded log trace.
On Friday, March 22, 2013 8:20:29 PM UTC-4, Adam Bradley wrote:
+1 on getting debugging working. I too use Aptana and now its no longer
working, so I will be reverting back to 1.7.5. However, doing this also
scares me because I do not want to be left behind and not stay up with the
latest and greatest features you guys are putting together. I love GAE, but
putting together documentation on how to debug would really help me out,
and since I do not know the in's and out's of the new dev server I'd rather
not try to figure it all out by myself (or if its even possible I can't
tell).
Love what you guys are doing and want to stay with the updates, but 1.7.6
is the first update that's put my development to a halt. Any advice on how
to get debugging working would be great.
Thank you,
Adam
On Tuesday, March 19, 2013 7:57:02 PM UTC-5, Andrew Jessup wrote:
In the 1.7.6 release of App Engine we’ve included a major upgrade to the
Development Server in the Python SDK, designed to make development faster
and more faithfully reproduce the production App Engine runtime
environment. The new version more faithfully simulates elements of the
production App Engine environment, such as concurrent requests and
backends, and in most cases this will also mean your apps run faster. We
previously included this in the 1.7.5 release as dev_appserver2.py, in this
release it has become the default dev_appserver.py
While we're confident the improvements are substantial, as with any
major change, some things work a little differently with the new
dev_appserver. Here’s a few changes to watch out for:
- Your local development admin console will run on it’s own server
and port, rather than under /_ah/admin
- We’ve changed the defaults for new applications, such as using HRD
rather than Master/Slave, and using SQLlite to emulate the datastore.
- We’ve cleaned up many command line flags and arguments
- Python 2.5 applications are no longer officially supported on the
new Development Server in line with our deprecation announcement
(although
they may still be run)
We’ve provided a detailed summary of all the changes to the Development
Server in our
documentationhttps://developers.google.com/appengine/docs/python/tools/old_devserver.
The the legacy dev_appserver.py remains available in the Python SDK as
old_dev_appserver.py for those who still require it. However if you
encounter any issues with the new Development Server we strongly encourage
you to report them on our issue
trackerhttps://code.google.com/p/googleappengine/issues/list
.
We hope you like the new changes, and that you enjoy snappier app
development with fewer surprises on deployment. Keep on coding!
- Andrew Jessup, for the App Engine team
--
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
