Re: Upgrading elpa packages results in Lisp nesting exceeds max-lisp-eval-depth...

[Stefan Monnier]

>> Indeed it's a bug in async.el.
>> Does the patch below help?
> I can't really test anymore, since all packages are updated now...but
> evaluating (async-bytecomp-get-allowed-pkgs) gives me

There's no async-bytecomp-get-allowed-pkgs any more, so if you're still
using it, it will break because it uses the old calling convention of
async-bytecomp--get-package-deps (which took a single package whereas
now it takes a list of packages).

> Even harder to test now since the fixed helm package appeared in this moment.

Actually, the most important test is to make sure it still works
correctly: I'm pretty sure it fixes the inf-recursion.


        Stefan