unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 10167@debbugs.gnu.org
Subject: bug#10167: 23.3; python.el code execution does not add the buffers directory to the pythonpath.
Date: Sun, 11 Dec 2011 20:57:21 +0100	[thread overview]
Message-ID: <1410245.gZC2tulmG3@fluss> (raw)
In-Reply-To: <dj8vmla3yw.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

Am Freitag, 9. Dezember 2011, 15:24:07 schrieb Glenn Morris:
> Arne Babenhauserheide wrote:
> > When calling python-send-buffer, the behaviour of the code differs
> > from actual code execution, because the parent directory of the file is
> > not in the PYTHONPATH.
> 
> I think this might be intentional?
> 
> http://lists.gnu.org/archive/html/emacs-devel/2008-09/msg00215.html

That’s quite inconvenient… would it not be cleaner to remove "" before 
importing emacs.py and add the buffer dir afterwards? 

For anything which is not emacs.py it is clear that it will be run. 
Alternatively add a new command which adds the buffer-dir - as I did for 
python-send-buffer.

(my changes would be cleaner by the way if I removed the path after the code 
again)

Best wishes, 
Arne
--
singing a part of the history of free software: 

- http://infinite-hands.draketo.de


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2011-12-11 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 10:39 bug#10167: 23.3; python.el code execution does not add the buffers directory to the pythonpath Arne Babenhauserheide
2011-12-09 20:24 ` Glenn Morris
2011-12-11 19:57   ` Arne Babenhauserheide [this message]
2012-01-27  7:50     ` Chong Yidong

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=1410245.gZC2tulmG3@fluss \
    --to=arne_bab@web.de \
    --cc=10167@debbugs.gnu.org \
    --cc=rgm@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 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).