From: Lawrence Liu <smartlitchi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andreyk.mad@gmail.com, emacs-devel@gnu.org
Subject: Re: python: Let pdb tracking not kill buffers
Date: Tue, 8 Oct 2019 00:26:24 +0800 [thread overview]
Message-ID: <CANYRarBCqVhU5aFGccFV6DGNqxM6OC7YmzsY08bfG42Px1rPPw@mail.gmail.com> (raw)
In-Reply-To: <83wodgzfxj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
I think the main reason is because sometimes,
the entires of our program is not a python file, it might be launch of a
docker image, a gunicorn application, even a background task etc. or it
might be wrapped by some 3rd launcher.
And sometimes it will coming through many steps before hit the break point.
Eli Zaretskii <eliz@gnu.org>于2019年10月8日 周二00:19写道:
> > From: Lawrence Liu <smartlitchi@gmail.com>
> > Date: Mon, 7 Oct 2019 12:33:17 +0800
> > Cc: Andrii Kolomoiets <andreyk.mad@gmail.com>, emacs-devel@gnu.org
> >
> > I am a full time python developer and seems in my case mostly I am using
> the way as below:
> >
> > insert a
> >
> > import pdb; pdb.set_trace();
> >
> > in my code bass and trigger the break point from other place (mostly
> browser) and wait for the break point
> > been hit.
>
> Any reason you don't use "M-x pdb" instead?
>
--
Best Regards
Lawrence
[-- Attachment #2: Type: text/html, Size: 1670 bytes --]
next prev parent reply other threads:[~2019-10-07 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 20:32 python: Let pdb tracking not kill buffers Andrii Kolomoiets
2019-10-05 6:40 ` Eli Zaretskii
2019-10-07 4:33 ` Lawrence Liu
2019-10-07 16:19 ` Eli Zaretskii
2019-10-07 16:26 ` Lawrence Liu [this message]
2019-10-07 12:28 ` Andrii Kolomoiets
2019-10-30 19:14 ` Andrii Kolomoiets
2019-11-01 9:35 ` Eli Zaretskii
2019-11-02 16:37 ` Andrii Kolomoiets
2019-11-02 17:29 ` Eli Zaretskii
2019-11-02 18:51 ` Andrii Kolomoiets
2019-11-07 16:57 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANYRarBCqVhU5aFGccFV6DGNqxM6OC7YmzsY08bfG42Px1rPPw@mail.gmail.com \
--to=smartlitchi@gmail.com \
--cc=andreyk.mad@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.