Naoya Yamashita
Naoya Yamashita
> Presumably this is because use-package tries to load evil ... while byte-compiling. This is one of the odd use-package behavior. (I think. I know this behavior comes from different...
Why do you compile `*-pkg.el` file when `;; no-byte-compile: t` is specified?
Please tell me(us) the step to reproduce?
Also, backtrace is very useful for this kind of bug report.
Please try `:mode` instead of `:init`. ```elisp (use-package pdf-tools :mode ("\\.pdf\\'" . pdf-view-mode)) ```
Good! Either way, package.el can recognize the dependencies correctly. It is important for package.el to recognize the dependencies in order to schedule the byte-compile order correctly.
If just suppress the compile error, the users will get an error at runtime. I recommend either splitting the package or add `packageage-require`. I prefer the former method. There are...
related to #1239. hi @rednafi, your suggestion is better than mine. Could you create your PR?
How about this? ```python def get_human(name): first_name, last_name = name.split() return Person(first_name, last_name) ```
related to #1239