Thanks for the info Andrew, I figure that startup script was the way to go but wasn't sure on how. I think that you need to figure how to release a version that wouldn't required manual wireup for debugging on at least make it very easy to do.
On Thursday, March 21, 2013 6:50:20 AM UTC+2, Andrew Jessup wrote: > > Hi Shay, > > A key goal of the new development server was to provide a runtime > environment closer to how your apps actually run in production, which is > why a single app will now often run in multiple processes. This raises an > interesting debugging challenge - how do we easily bind the right process a > debugger to, particularly if that process hasn't started yet? How do we > prevent that process from being automatically restarted should you change > the file? > > In our open source mirror project for the new dev_appserver we've added > some additional flags that allow you to more tightly control process > execution and provide hooks that allow you to write scripts to control how > and where to attach a debugger. We hope to tighten this API and include > with dev_appserver it in the next release of the App Engine SDK. > > If you'd like to take a look now, I would point you to this discussion > https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28and > in particular the document linked there that summarizes our proposed > debugging approach and provides some sample code to get started. > > > > > On Thu, Mar 21, 2013 at 1:27 AM, Shay Erlichmen > <[email protected]<javascript:> > > wrote: > >> I worked with preview version of it and I was too embarrassed to ask, but >> now that this is official quick question: >> How do you debug code now? in the old dev server (under eclipse + pydev) >> all I have todo is set a breakpoint it seem now that this is no longer >> working (latest pydev + juno). >> I imagine that I can attach to the process but please tell me that this >> is not the optimal way. >> >> >> On Wednesday, March 20, 2013 2:57:02 AM UTC+2, 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 >>> documentation<https://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 >>> tracker<https://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 [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > > Andrew Jessup | Product Manager, Google App Engine | > [email protected]<javascript:> > > -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
