unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Philip Kaludercic <philip.kaludercic@fau.de>,
	 emacs-devel@gnu.org, monnier@iro.umontreal.ca
Subject: Re: ELPA submission: python-import
Date: Sun, 31 Jul 2022 11:20:14 +0200	[thread overview]
Message-ID: <874jyxr641.fsf@gmail.com> (raw)
In-Reply-To: <E1oHzgS-0003t8-2V@fencepost.gnu.org> (Richard Stallman's message of "Sat, 30 Jul 2022 23:32:04 -0400")

On Sat, 30 Jul 2022 at 23:32, Richard Stallman <rms@gnu.org> wrote:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > I am not saying it isn't impossible, but if there is a dependency on
>   > project.el, it might make sense to raise the minimum version of ELPA's
>   > python.el?
>
> Is it necessary for any of these python files depend on project.el?
> If these features such as python-import  are added to python.el,
> doesn't it eliminate the need for that?

AFAICT, there's nothing in python.el that helps figuring out which
project a buffer belongs to, or, say, list all files belonging that
project (which exactly is what project.el does).

python-mode mainly provides functionality to edit individual Python
files, but it's natural to add things that need to know about the
project as well.  Import management is one of them; another interesting
feature would be a Python shell that is not "global" but rather
dedicated to a project (in the same vein as `project-shell').

So I think it makes sense for python.el (and prog-modes in general) to
rely on project.el to implement some more advanced features.



  reply	other threads:[~2022-07-31  9:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 14:15 ELPA submission: python-import Augusto Stoffel
2022-07-29 15:18 ` Eli Zaretskii
2022-07-29 15:35   ` Augusto Stoffel
2022-07-29 16:25     ` Stefan Monnier
2022-07-30  8:56       ` Augusto Stoffel
2022-07-31  3:28       ` Richard Stallman
2022-07-31  9:08         ` Augusto Stoffel
2022-07-29 15:53 ` Philip Kaludercic
2022-07-30  9:07   ` Augusto Stoffel
2022-07-30  9:12     ` Visuwesh
2022-07-30 11:14       ` Augusto Stoffel
2022-07-30 11:58     ` Philip Kaludercic
2022-07-30 19:01       ` Augusto Stoffel
2022-07-31  9:22         ` Philip Kaludercic
2022-07-31  3:32       ` Richard Stallman
2022-07-31  9:20         ` Augusto Stoffel [this message]
2022-07-31  9:26         ` Philip Kaludercic
2022-07-31 10:46           ` Stefan Monnier
2022-07-31  3:28   ` Richard Stallman

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=874jyxr641.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philip.kaludercic@fau.de \
    --cc=rms@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).