[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA submission: python-import
From: |
Augusto Stoffel |
Subject: |
Re: ELPA submission: python-import |
Date: |
Sun, 31 Jul 2022 11:20:14 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
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.
- Re: ELPA submission: python-import, (continued)
Re: ELPA submission: python-import, Philip Kaludercic, 2022/07/29
Re: ELPA submission: python-import, Richard Stallman, 2022/07/30
Re: ELPA submission: python-import,
Augusto Stoffel <=
Re: ELPA submission: python-import, Philip Kaludercic, 2022/07/31
Re: ELPA submission: python-import, Stefan Monnier, 2022/07/31
Re: ELPA submission: python-import, Richard Stallman, 2022/07/30