unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: 31410@debbugs.gnu.org
Subject: bug#31410: (no subject)
Date: Sat, 28 Aug 2021 12:05:00 +0200	[thread overview]
Message-ID: <87fsutevg3.fsf@gmail.com> (raw)
In-Reply-To: <87r2mj30t6.fsf@k-7.ch>

> When reading Python.el source code, I see it's support Python virtual
> environment by setting the variable 'python-shell-vertualenv-root'

> It would be more discoverable if we have an interactive function to do
> that. Somthing like 'python-virtualenv' or similar. The must would be to
> have a key binding for it and eplained it in mode help.

This is just an opinion, but I think the virtualenv support in the
Python shell is a misguided feature.  The problem is that it merely sets
up the shell to run in a given virtualenv; it has no influence on other
external tools such as language servers or, say, ‘M-x compile RET pytest
RET’.

Instead, it would be better to embrace the idea of setting the
‘process-environment’ and ‘exec-path’ variables buffer-locally.  There
are some rough edges to be polished, cf [1].  But at least there are
packages, such as envrc, direnv and buffer-env (on MELPA) to help
managing env vars in Emacs.

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46345





      reply	other threads:[~2021-08-28 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 16:58 bug#31410: 25.3; Python.el: Support for Python virtual environment (venv) Sébastien Gendre
2021-08-28 10:05 ` Augusto Stoffel [this message]

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=87fsutevg3.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=31410@debbugs.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).