Re: ELPA submission: python-import

[Philip Kaludercic <philipk@posteo.net>]

Augusto Stoffel <arstoffel@gmail.com> writes:

> On Sat, 30 Jul 2022 at 13:58, Philip Kaludercic <philip.kaludercic@fau.de> wrote:
>
>> 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?  Alternatively, one could try and reduce the minimum version
>> of project.el, but that might be tricky.
>
> That would be very desirable (respectively sad if impossible).  One of
> the improvements I would like to propose next is a project-dedicated
> version of the Python shell (analogous to project-shell).
>
> So that's already 2 features that would depend on project.el.

I'd say we should ask the maintainer of python.el, but there appears to
be nobody who is explicitly responsible for that file.  I'd say that
Emacs 26.1 is old enough to legitimise updating the minimum version.

> In principle it should be possible to declare that users of Emacs ≤ 26
> need to stick to python.el ≤ 0.28, but I guess the package manager
> doesn't allow this kind of thing, right?

No, the "archive-contents" doesn't appear to only contain the
information for a single version of a package.

>> We have recently added compat as a dependency for ERC, but that only
>> required support back until 27.1.  Sadly it isn't as simple as just
>> adding (require 'compat nil 'noerror) at the top of the file, as compat
>> is neither complete not transparent.
>
> Okay, for sure compat doesn't free you from knowing about the history of
> the features and limitations of the compat replacements.  But is there
> any deeper reason why adding (require 'compat nil 'noerror) can be
> problematic?

Currently, not to my knowledge.  But there hasn't been any feedback on
ERC's recent change, so this might change.