Dear Salman, Thank you for reporting this bug and bringing the issue to my attention. P.S. I'm treating this bug as a mentoring opportunity instead of just fixing and closing, because we've worked together on MRs for this package, but let me know if you'd rather I take care of it :-) Salman Mohammadi <salman@smoha.org> writes: > A fresh installation of elpa-elpy does not install > elpa-find-file-in-project automatically and running the command C-c C-f > shows us this warning message: > > elpy-find-file: ‘elpy-find-file’ necessitates ‘projectile’ or > ‘find-file-in-project’ to be installed. > With the new release upstream made ffip optional, and this message indicates that the user can enable the desired functionality using either projectile or ffip. I'm of course biased towards ffip because I use it, and maintain it and its dependency ivy. As much as I'd like to encourage users to use the software I work on and use by forcing them to install it, that position isn't supported by Policy §7.2 [1]. Please take the time to read it, and reply with which of the five dependency types is most correct for this case--and why. Keep in mind we try to accommodate users who prefer to install as little as possible (to a reasonable degree), the users who want "everything and the kitchen sink", and everyone in between these two poles (the majority). While I might not be online when you are, someone at #debian-emacs or #debian-mentors should be willing to discuss §7.2. I plan to put the following in the appropriate field, preferring ffip, because 1) It was previously a required dep 2) I don't know if projectile works "out of the box", and I'm more comfortable supporting ffip as a first choice 3) Elpy docs §"IDE Features" claims they're alternatives to each other for the purpose of `elpy-find-file` 4) What is probably the cause of #948567: elpa-find-file-in-project | projectile > But as I checked the control file, elpa-find-file-in-project is in > Build-Depends. > This is because one or more unit tests depend on it. Optional functionality that requires additional packages should be tested at build time. IIRC autopkgtest-pkg-elpa is installing the Build-Depends in the autopkgtest environment, which is why they also pass there. Regards, Nicholas [1] https://www.debian.org/doc/debian-policy/ch-relationships.html
Attachment:
signature.asc
Description: PGP signature