jorgenschaefer
Status of fork
On my fork of elpy, I have a branch that fixes the structure of many of the original tests. The tests were not runnable because they contained duplicate test names, causing ert to refuse to load them. After repairing the tests, on my laptop I get the following test failures:
23 unexpected results:
FAILED elpy-company-backend-should-add-shell-candidates
FAILED elpy-company-backend-should-find-full-prefix-string
FAILED elpy-company-backend-should-find-simple-prefix-string
FAILED elpy-config--get-config-should-return-keys
FAILED elpy-config--get-config-should-set-pythonpath
FAILED elpy-eldoc-documentation-should-show-object-onelinedoc
FAILED elpy-fold-at-point-should-NOT-fold-and-unfold-functions-from-after
FAILED elpy-multiedit-python-symbol-at-point-should-save-some-buffers
FAILED elpy-pdb-break-at-point-should-break-at-point
FAILED elpy-pdb-debug-buffer-and-break-at-point-should-ignore-breakpoints
FAILED elpy-pdb-debug-buffer-from-beginning-should-enter-pdb
FAILED elpy-pdb-debug-buffer-should-always-begin-at-first-line
FAILED elpy-pdb-debug-buffer-should-continue-with-second-breakpoint
FAILED elpy-pdb-debug-buffer-should-enter-pdb
FAILED elpy-pdb-debug-buffer-should-forget-previous-breakpoints
FAILED elpy-pdb-debug-buffer-should-stop-at-the-first-breakpoint
FAILED elpy-pdb-debug-last-exception-should-debug-last-exception
FAILED elpy-pdb-debug-last-exception-should-ignore-breakpoints
FAILED elpy-pdb-toggle-breakpoint-at-point-should-add-breakpoints
FAILED elpy-rpc-get-virtualenv-path-should-return-current-venv-path
FAILED elpy-shell-send-file-should-accept-large-strings
FAILED elpy-shell-should-echo-outputs
FAILED elpy-should-format-code-with-default-formatter
I'll work on fixing these, as time permits, if anyone else is interested in my work.
That is amazing! Feel free to create a PR. I don't have time to write elisp these days but would gladly do reviews.
@rpgoldman I just want to thank you for contributing back to elpy, I recently tested different python setups for emacs, tested elpy along the way and remembered how perfect my previous elpy python dev environment used to feel.
I may be unlikely to contribute to elpy but will gladly support anything and anyone who keeps it running as I can.
hey @rpgoldman appreciate the previous PR's!
Curious if you've had time to work on any more test updates. Thanks again!
@gopar I'm afraid not. I've been swamped with other things and at the moment I'm struggling with multiple different bits of python editing that are interacting:
- Virtual environments (including possibly poetry)
- The rpc virtual environment. E.g., for tools like
mypy, the linting tool must have access to the python environment running the code being edited, rather than being in a separate virtual environment. - flycheck/flymake
- eglot
All of these are making my head swim!