|New experimental development server for Python||Brian Quinlan||11/26/12 6:15 PM|
I'm happy to announce that the App Engine team is working on a new
development server for Python (and eventually Go).
The new development server aims to provide higher performance for
complex applications and better emulation of the App Engine deployment
There are several features that are currently missing:
- support for backends
- the administrative UI (i.e. _ah/admin)
Development is still at an early stage so I'm sure that there are lots
of bugs to be found and fixed.
Which is why we'd appreciate your help in testing and, if you are
feeling keen, fixing these issues.
You can download the latest version from:
Or work directly with the git repository:
There is also a public discussion group associated with the project:
Thanks for your help!
Brian - App Engine Python Team
|Re: [google-appengine] New experimental development server for Python||alex||11/27/12 12:48 AM|
Brian, this is awesome!
I've already tried it with a side project of mine that uses task
queues and urlfetch. Even though it runs a couple backends too, the
code already handles different cases, dev vs production, because of an
open issue with addressing backends (5105). It all runs smoothly!
Really appreciate putting the tests in the repo. Love it.
I'll try using it for my other apps and see how it goes.
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
|Re: New experimental development server for Python||Kaan Soral||11/28/12 2:11 PM|
Great to hear :)
I will also test it out some time.
Now we can finally test our apps on all browsers before production.
|Re: New experimental development server for Python||Brian Quinlan||12/11/12 8:59 PM|
We have released a new version of the development server:
- threads are implicitly joined on request exit
- basic taskqueue UI (more later)
- fixes for virtualenv
- windows unit test fixes
- reduced logging noise
- correct logout url generation
As always, feedback is welcome!
|Re: [google-appengine] Re: New experimental development server for Python||PK||12/11/12 10:47 PM|
More regression tests pass now but one of them fails with the message below. I am on 1.7.3, all my tests pass with the regular dev server.
BadRequestError: remote_api supports transactional queries only in the high-replication datastore.
Is this something consistent with the bugs you already track?
|Re: [google-appengine] Re: New experimental development server for Python||PK||12/11/12 10:54 PM|
I looked in more detail the stack trace and hits an issue I had seen before that was fixed when bug 3643 was fixed. The bug was fixed in 1.7.2, I am wondering whether you could have forked some code before that fix went in?
|Re: [google-appengine] Re: New experimental development server for Python||Brian Quinlan||12/13/12 3:53 PM|
Thanks for the bug description! We understand the cause (the lack of
the "dev~" prefix on app ids) and will fix it soon .
 "soon" may not be that soon due to the holidays :-)
|Re: [google-appengine] New experimental development server for Python||PK||12/13/12 5:30 PM|
OK Thanks... I filed issue #16 to track it.
Another test code showstopper, is the following:
We have some test code that waits until all tasks have executed and only then continues. The way it does this is by scraping the /_ah/admin/queueues page until all the counters are 0. Without admin console this part also fails. I assume you will provide an admin console at some point so this will take care of it.
(BTW, this is really old ugly code that will also fail next time the UI changes, it is probably time to start using the QueueStatistics for the same purpose, incidentally it just became fully supported with 1.7.4).
|Re: [google-appengine] New experimental development server for Python||Brian Quinlan||12/13/12 5:52 PM|
On Fri, Dec 14, 2012 at 12:30 PM, PK <p...@gae123.com> wrote:Thanks!
Could you try adding this to your app.yaml:
- url: /admin_console/.*
|Re: New experimental development server for Python||Sam McNally||12/19/12 7:41 PM|
We have released a new version. Download it from http://code.google.com/p/appengine-devappserver2-experiment/downloads/detail?name=devappserver2-v0.4.zip
New in this version:
- backends with support for background threads
- admin UI for cron, datastore indexes and inbound mail
- improved taskqueue UI
|Re: New experimental development server for Python||Brian Quinlan||1/20/13 8:11 PM|
We have released a new version of the experimental Python development server. We think that it is very usable at this point and has some significant improvements over the existing version.
- a functionally complete administrative UI (it is also a lot more polished but still needs some work)
- more reliable task execution
- (experimental) support for local Cloud SQL development
- lots of bug fixes!
As always, feedback is very welcome!
On Tue, Nov 27, 2012 at 1:14 PM, Brian Quinlan <bqui...@google.com> wrote:
|Re: [google-appengine] Re: New experimental development server for Python||Jeff Schnitzer||1/23/13 11:38 AM|
Do background threads work? Whenever I try to start one, I get
|Re: [google-appengine] Re: New experimental development server for Python||Brian Quinlan||1/23/13 12:50 PM|
That should work.
Are you creating a background thread on a frontend or a backend instance?
On Thu, Jan 24, 2013 at 6:38 AM, Jeff Schnitzer <je...@infohazard.org> wrote:
|Re: [google-appengine] Re: New experimental development server for Python||Jeff Schnitzer||1/23/13 6:41 PM|
It's a resident backend.
|Re: [google-appengine] Re: New experimental development server for Python||Brian Quinlan||1/23/13 8:31 PM|
On Thu, Jan 24, 2013 at 1:41 PM, Jeff Schnitzer <je...@infohazard.org> wrote:Are you sure that this happens on the first attempt to create a
background thread? If so, then could you could try to find this block
+ logging.exception('Cannot create background thread.'
And see what logging you see?
|Re: New experimental development server for Python||Brian Quinlan||2/5/13 11:06 PM|
We have released a new version of the new Python development server.
This development server will replace the existing one in the 1.7.6
release so we'd greatly appreciate any feedback.
- Add a blobstore viewer (thanks Alex!)
- Several UI improvements (thanks Alex)
- Add protorpc support
- Add automatic conversion from the datastore file stub to the sqlite stub.
- Add update checking
- Allow starting background threads from backends handling /_ah/start requests.
- Set DEFAULT_VERSION_HOSTNAME
- Avoid crashing on empty backends
- Set environ['SERVER_NAME'] to match environ['HTTP_HOST']
- Make exception logging more robust
- Bypass login: required for inbound xmpp requests from the admin UI
- Stop raising KeyboardInterrupts in async_quit and for SIGTERM and SIGINT
- Gracefully handle the case where 'headers' or 'response_code' are not set
- Always filter x-appengine-fake-is-admin and x-appengine-fake-logged-in headers
|Re: New experimental development server for Python||Jacob G||2/8/13 6:31 AM|
This new development server sounds very exciting. I haven't had a chance yet to try it, but I look forward to checking out all these great features.
One question I have is regarding your bullet point "Add automatic conversion from the datastore file stub to the sqlite stub." Does this feature address the conversion failure problem discussed here:
|Re: [google-appengine] Re: New experimental development server for Python||Brian Quinlan||2/8/13 11:48 AM|
On Sat, Feb 9, 2013 at 1:31 AM, Jacob G <ja...@fareclock.com> wrote:I don't understand the reason for that failure so I can't say for
sure. It looks like the discussion is ongoing here:
> --> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengi...@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.
|Jacob G||2/18/13 6:52 AM||<This message has been deleted.>|
|Re: New experimental development server for Python||Brian Quinlan||2/24/13 9:28 PM|
We have released a new version of the Python development server. This
version will be included in the App Engine 1.7.6 SDK release so any
testing or other feedback would be greatly appreciated!
Aside from a long list of bug fixes, this version adds experimental Go support!
To download the cross-platform package for Python:
To download the Linux amd64-only package for Python and Go:
- Fixes testbed support
- Tests now pass on Windows and Mac OS X
- Multiple set-cookies headers no longer combined
- Some minor UI improvements
- Invalid login cookies are ignored
- Go runtime support!
- Use a threadsafe subprocess implementation
- Fixed Google Cloud SQL support on windows
- use mtime checking for config file update checks
- switch to one thread per async work item
- set the backlog for WsgiServer sockets to 100
|Re: New experimental development server for Python||pdknsk||2/26/13 1:24 AM|
I can only recommend to try it.
|Re: New experimental development server for Python||Brian Quinlan||3/10/13 11:12 PM|
We have released a new version of the Python development server. A descendant of this version will be included in the App Engine 1.7.7 SDK release so any testing or other feedback would be greatly appreciated!
- Cloud Endpoints (see http://goo.gl/m2GjG)
- Integration points for Python tools (see http://goo.gl/3oSBp)
- Add support for tasks that target backends
- Fix the size display in blobstore viewer
- Fix the styling of the "Purge" button in the taskqueue UI
- Make --log_level=debug display debug-level logging
|Re: New experimental development server for Python||michael kariv||4/23/13 2:00 AM|
I have installed 1.7.7.
I have read through the document.
The document gives us hope, because as of now PyDev debugging (setting a breakpoint in the app code) does not work.
I have tried to implement the document, and so far I can connect remote debugger to the instance and see logging.info() printouts, but I still can not set a breakpoint
My detailed account of what I did is here: