From: Augusto Stoffel <arstoffel@gmail.com>
To: Philip Kaludercic <philip.kaludercic@fau.de>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: ELPA submission: python-import
Date: Sat, 30 Jul 2022 11:07:33 +0200 [thread overview]
Message-ID: <871qu3klyi.fsf@gmail.com> (raw)
In-Reply-To: <871qu3synn.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 29 Jul 2022 17:53:48 +0200")
Hi Philip,
See my response to your comments below.
But more importantly, since now the plan is to add those features to
python.el, which is built-in but also extracted to be distributed on
ELPA for Emacs ≥ 24.4 --- have you thought of a scheme whereby one could
use new Emacs features on those kinds of packages, but then
automatically stick a (require 'compat) at the top of their ELPA
version?
On Fri, 29 Jul 2022 at 17:53, Philip Kaludercic <philip.kaludercic@fau.de> wrote:
> Why do you depend on Emacs 28.1? Setting aside convenience functions
> like length=, all you really need is project-files from Emacs 27.1,
> right? And if you add a dependency on the right version of project.el
> that implemented that function, you could even reduce the (transitive)
> dependency to Emacs 26.1.
I'm also using the MODES argument of the `interactive' form. But yes, I
have no good reason to require 28 other than being unfamiliar/not
remembering the history of the new features, which makes it hard to
"promise" compatibility with older Emacsen.
> I am not familiar with isort, and I suppose there are other lightweight
> Emacs users like me who haven't heard of it either. It might therefore
> be good to add a link to some documentation, especially on how to
> install it since that can sometimes be tricky when using Python.
Sure, I'll will do that.
next prev parent reply other threads:[~2022-07-30 9:07 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 [this message]
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
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=871qu3klyi.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philip.kaludercic@fau.de \
/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).