unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: kobarity <kobarity@gmail.com>, Augusto Stoffel <arstoffel@gmail.com>
Cc: pmercatoris <mercatorispierre@gmail.com>, 60142@debbugs.gnu.org
Subject: bug#60142: 28.1; python.el Incorrect region when python-shell-send-region from indented code
Date: Sun, 18 Dec 2022 12:39:01 +0200	[thread overview]
Message-ID: <83mt7lf12y.fsf@gnu.org> (raw)
In-Reply-To: <NAA0NR.HZSFGGGOVVZN@gmail.com> (message from pmercatoris on Fri,  16 Dec 2022 23:54:23 +0100)

> Date: Fri, 16 Dec 2022 23:54:23 +0100
> From: pmercatoris <mercatorispierre@gmail.com>
> 
> I am unable to get correct behavious when sending a region from indented code
> to the python shell. Consider this python code:
> 
> ```python
> if True:
>     if True:
>         a = "test"
> ```
> 
> If I select the first `True` and `python-shell-send-region`, it will
> correctly send it to the consol and print `True`.
> 
> Now if I do the same thing with the second `True` it will throw an
> error: `IndentationError: expected an indented block after 'if'
> statement on line 1` Although it would also reffer to unexpected block
> after `if` even it it were `for`, `try`, ...
> 
> If I select the `a` or `a = "test"` it will correctly send it to the
> console, however it won't echo the evaluation of the statement.
> 
> If I select the string "test" and send, it will throw the same error as
> the second True.
> 
> My python config is very minimal:
> 
>   (use-package python
>     :ensure nil
>     :mode
>     ("\\.py\\'" . python-mode)
> 
>     :init
>     (setq-default indent-tabs-mode nil)
> 
>     :config
>     (setq python-indent-offset 4
>           python-indent-guess-indent-offset-verbose nil
>           )
> 
>     (setq python-shell-interpreter "jupyter"
>           python-shell-interpreter-args "console --simple-prompt"
>           python-shell-prompt-detect-failure-warning nil)
> 
>     (add-to-list 'python-shell-completion-native-disabled-interpreters
>                  "jupyter"))

Could you two please look into this?  It sounds to me like Emacs works
as expected here, but I'm not an expert on Python and our interfaces
with it.

Thanks.





  reply	other threads:[~2022-12-18 10:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 22:54 bug#60142: 28.1; python.el Incorrect region when python-shell-send-region from indented code pmercatoris
2022-12-18 10:39 ` Eli Zaretskii [this message]
2022-12-18 15:04   ` Pierre Mercatoris
2022-12-18 22:25     ` kobarity
2022-12-19  3:28       ` Eli Zaretskii
2022-12-19 10:25   ` Augusto Stoffel
2022-12-22 15:01     ` kobarity
2022-12-30 13:14       ` Pierre Mercatoris
2022-12-30 15:33         ` kobarity
2022-12-30 16:36           ` Pierre Mercatoris
2022-12-31  7:23             ` kobarity
2022-12-31  8:17               ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mt7lf12y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60142@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=kobarity@gmail.com \
    --cc=mercatorispierre@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).