pyenv exited with status 127 when using pet-mode with emacs-jupyter about emacs-pet HOT 5 CLOSED

Fair enough! I have a hacky workaround atm using (when buffer-file-name ...) (as those org-src-edit buffers don't have a file name), but will send an email to the org-mode maillist to ask for their advice.

In any case I'm closing this issue as it is not related to PET. Thanks for the replies, and thanks for this great package which is making my Python package development process a lot easier :)

from emacs-pet.

What's your project layout? Where did you install jupyter? Can you give me a trace of pet-executable-find and/or pet-virtualenv-root?

from emacs-pet.

Thanks for the suggestion to trace those functions! (Sorry still relatively new to Elisp).

See below for the trace. Reading it it seems that the error is caused by the executables it could not find (and therefore returning nil). This makes sense as I do not have those packages (e.g. black) installed in the project venv.

Do you have any suggestions on how to configure pet to avoid running python-pet-hook for org-src blocks? In my normal Python projects I do use these tools, so I would like to keep them in python-pet-hook. I just need them to not search for the executables for my Org notebooks.

I have tried the following without results:

(use-package pet
  :elpaca t
  :hook
  (python-mode . python-pet-hook)
  (org-src-mode. org-src-pet-hook)
  :init
  (defun python-pet-hook ()
    (unless (org-src-edit-buffer-p)
	(pet-mode)))
  (defun org-src-pet-hook ()
    (remove-hook 'python-mode-hook 'python-pet-hook t)))

I have also tried variants with org-in-src-block-p and (bound-and-true-p org-src-mode) without succes. Any suggestions?

======================================================================
1 -> (pet-executable-find "python")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: "/Users/duynguyen/.pyenv/versions/3.10.5/bin/python"
======================================================================
1 -> (pet-virtualenv-root)
1 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
======================================================================
1 -> (pet-executable-find "jedi-language-server")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: nil
======================================================================
1 -> (pet-executable-find "pytest")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: nil
======================================================================
1 -> (pet-executable-find "black")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: nil
======================================================================
1 -> (pet-executable-find "isort")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: "/Users/duynguyen/.local/bin/isort"
======================================================================
1 -> (pet-executable-find "yapf")
| 2 -> (pet-virtualenv-root)
| 2 <- pet-virtualenv-root: "/Users/duynguyen/.venv/"
1 <- pet-executable-find: "/Users/duynguyen/.local/bin/yapf"

from emacs-pet.

I don't know. I don't use org-mode. AFAIK, similar modes like polymode and markdown-mode have(had) the same problem. This is a problem with how Emacs expose major mode switching lifecycle hooks and how these modes reuse major modes in source code blocks. There's nothing you can do about it at the moment, but perhaps you can file a ticket to Emacs.

from emacs-pet.

Alternatively, you may try to detect whether you are in a project in your hook, and only activate pet mode when you are.

from emacs-pet.