+1. Debugger still can't attach from Eclipse by setting breakpoints the
way you used to with anything past 1.7.5.
Anyone had any success?
On Friday, August 9, 2013 4:07:30 PM UTC-7, Andrew Jessup wrote:
>
> Good news everyone!
>
> We just wanted to give you a quick update on PDB debugging suppo
Good news everyone!
We just wanted to give you a quick update on PDB debugging support in the
new dev_appserver.
One of the key design goals of the new dev_appserver was to provide a more
faithful emulation of how your application performs in production -
including servicing each incoming r
Debugging is still a problem.
This link below was posted by Brian Quilan in a different thread
https://docs.google.com/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit#heading=h.fj44xnkhr0gr
Here is where I am trying to solve the problem:
1. breakpoints DO WORK if you set them in dev_
I have new server working for me on windows 7 32bit running in a VMWare
virual machine, hosted by windows 7 64 bit.
I use 1.7.7, not 1.7.6
If you can send me a synthetic test of your problem I'll try and run on my
environment
On Monday, April 22, 2013 6:20:18 PM UTC+3, David wrote:
>
> Looks lik
there is a setting for id allocation, didn't check the actual setting right
now, but those big ids recently started showing up, 'scattered' should be
the default, you can change it to sequential or something like that, it
might be worthwhile to check --help for this
I see a lot of chatter aroun
Looks like dev_appserver2.py does NOT work on 32 bit Windows.
It crashes 32 bit python on the huge id()
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 t
I posted this a few weeks ago, on how to debug 1.7.6 using Boa.
https://groups.google.com/forum/#!topicsearchin/google-appengine/Boa/google-appengine/-m00Qz4Vc7U
Its not hard to do
The same approach will no doubt work with winpdb,
T
On Sunday, April 21, 2013 5:12:42 AM UTC+8, Adam Bradle
Has anyone come up with a way to debug? I obviously must be missing
something because I find it hard to believe its no longer possible. For
anyone who has no issues debugging, please share any advice you may have on
how to setup local dev environments (since 1.7.6 that is). Thanks
--
You recei
>
>- We’ve cleaned up many command line flags and arguments
>
>
Is there any place where we can see which arguments have been removed and
workarounds?
And, please, I can't believe debugging is not possible now... that is
really really incredible, I will stay with 1.7.5 until you have found
For those discussing whether or not to upgrade to 1.7.6— the legacy dev app
server remains available in the Python SDK as 'old_dev_appserver.py'. So
you can upgrade to 1.7.6 and still access it.
-Amy
On 25 March 2013 08:21, Mehul Kar wrote:
> Should I wait on upgrading then? I use pdb.set_tra
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 p
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
+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
Debugging is an absolute necessity. I use Eclipse PyDev (well, actually
Aptana Studio) specifically because of the graphical debugger. I feel blind
when I don't have a debugger; It's one of the most useful tools I know of
for development. I'm sticking to 1.7.5 for this (and other) reasons.
- Br
+1 for debuging. I will keep the 1.7.5 version until Pycharm implements de
debuger.
Renzo
On Tuesday, March 19, 2013 9:57:02 PM UTC-3, 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 dev
Thanks for the suggestion, I will give it a try :)
Actually, the async nature of the devappserver also makes the logs just a
little hard to read, so I'm guessing the upcoming versions will come with
many new features, for example there seems to be a new log sqlite file that
is not yet used, If
On Friday, March 22, 2013 12:35:37 PM UTC-4, Kaan Soral wrote:
> No one forces anyone to use anything, you can always use previous versions
> of SDK/Devappserver
>
> They've stated why It's currently not possible to debug with
> devappserver2, as someone watching the development of devappserver2
No one forces anyone to use anything, you can always use previous versions
of SDK/Devappserver
They've stated why It's currently not possible to debug with devappserver2,
as someone watching the development of devappserver2 closely, I'm sure they
will come up with a way to satisfy your debuggin
On Thursday, March 21, 2013 12:50:20 AM UTC-4, Andrew Jessup wrote:
>
> 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 propos
The Python 2.5 deprecation blog post is here:
http://googleappengine.blogspot.com.au/2013/03/python-25-thanks-for-good-times.html
Cheers,
Brian
On 22 March 2013 05:58, Darien Caldwell wrote:
>
> On Tuesday, March 19, 2013 5:57:02 PM UTC-7, Andrew Jessup wrote:
>>
>> Python 2.5 applications are
On Tuesday, March 19, 2013 5:57:02 PM UTC-7, Andrew Jessup wrote:
>
> 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)
>
>
I must have missed that notification. I know 2.7 w
Disagree,
Debugging and hot patch is the killer feature. The problens with diferent
behavior of local and production was easily with a test or homolog
enviroment. On the other hand, using just log to fix and find bugs will
increase too much the development time. Until it is not solved, I will
I tried many times to use a debugger. Originally I was using the wing IDE, now
I am using pycharm. The main problem was that the debugger was just too slow so
almost always I ended up using log messages.
Don't get me wrong, fast debugging with "hot patching" would be great but i
never felt i h
I also notice that now I need to choose between debug and live code update
(AKA hot patching).
Debugging while code editing was one of killers features of the old server,
please find a solution for this also.
On Thursday, March 21, 2013 10:02:19 AM UTC+2, Shay Erlichmen wrote:
>
> Thanks for the
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
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
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 ima
I have opened an issue -
https://code.google.com/p/googleappengine/issues/detail?id=9007
--
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+u
28 matches
Mail list logo
