Cannot activate pipenv when the file gets opened via projectile

chama-chomo commented 4 years ago

Description :octocat:

When I open a file with dired, using ranger layer or run emacs 'file' directly from the terminal pipenv can be activated normally

Reproduction guide :beetle:

Start Emacs
SPC p p and choose project/file
activate pipenv with SPC m v a

Observed behaviour: :eyes: :broken_heart:

No virtualenv has been created for this project yet!
pipenv --venv exited abnormally with code 1
pipenv-activate: Wrong type argument: stringp, nil

Expected behaviour: :heart: :smile: pipenv activates virtual env.

System Info :computer:

OS: gnu/linux
Emacs: 26.3
Spacemacs: 0.300.0
Spacemacs branch: develop (rev. 239f60a65)
Graphic display: t
Distribution: spacemacs
Editing style: vim
Completion: helm

Layers:

((javascript :variables javascript-backend 'lsp)
helm command-log
(lsp :variables lsp-server-trace nil lsp-log-io nil lsp-eldoc-hook nil lsp-ui-doc-enable t lsp-ui-doc-header nil lsp-ui-doc-include-signature nil lsp-ui-doc-position 'top lsp-ui-doc-max-width 120 lsp-ui-doc-max-height 40 lsp-ui-doc-use-childframe t lsp-ui-doc-use-webkit t lsp-ui-sideline t lsp-ui-sideline-enable t lsp-ui-sideline-ignore-duplicate t lsp-ui-sideline-show-symbol t lsp-ui-sideline-show-hover nil lsp-ui-sideline-show-diagnostics nil lsp-ui-sideline-show-code-actions t lsp-ui-sideline-code-actions-prefix "" lsp-ui-peek-enable t lsp-ui-peek-peek-height 10 lsp-ui-peek-list-width 50 lsp-ui-peek-fontify 'always lsp-ui-flycheck-enable t lsp-cache-candidates t)
(python :variables python-backend 'lsp python-lsp-server 'pyls python-fill-column 99 python-enable-yapf-format-on-save nil python-sort-imports-on-save nil python-pipenv-activate nil python-test-runner 'pytest)
emacs-lisp json groovy dash
(neotree :variables neo-vc-integration
      '(face)
      neo-autorefresh t neo-theme 'icons)
(version-control :variables version-control-global-margin t version-control-diff-side 'left version-control-diff-tool 'diff-hl)
git imenu-list docker ansible plantuml salt markdown multiple-cursors
(org :variables org-enable-org-journal-support t)
copy-as-format yaml search-engine csv html
(ibuffer :variables ibuffer-group-buffers-by 'projects)
systemd confluence parinfer ranger dap
(auto-completion :variables auto-completion-enable-sort-by-usage t auto-completion-return-key-behavior 'complete auto-completion-tab-key-behavior 'cycle auto-completion-complete-with-key-sequence nil auto-completion-complete-with-key-sequence-delay 0.1 auto-completion-private-snippets-directory t auto-completion-enable-snippets-in-popup t spacemacs-default-company-backends
              '(company-lsp company-anaconda company-files company-capf)
              auto-completion-enable-help-tooltip t)
(shell :variables shell-default-term-shell "/bin/zsh" shell-default-shell 'eshell shell-default-height 30 shell-default-position 'bottom)
(syntax-checking :variables syntax-checking-enable-tooltips nil))

System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS GLIB NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD LCMS2

Backtrace :paw_prints:

<<BACKTRACE IF RELEVANT>>

Trapez commented 4 years ago

Set python-pipenv-activate to t.

chama-chomo commented 4 years ago

nope, it doesn't help

     (python :variables
             python-backend 'lsp
             python-lsp-server 'pyls
             ;; python-lsp-server 'mspyls
             ;; python-backend 'anaconda
             python-fill-column 99
             python-enable-yapf-format-on-save nil
             python-sort-imports-on-save nil
             python-pipenv-activate t

Trapez commented 4 years ago

Take a look at your .spacemacs.env file, any references to virtualenvs should be removed and make sure the path looks sane. That has usually been the reason for any strange behavior in the python layer for me.

chama-chomo commented 4 years ago

Unfortunately, I haven't found any references, I'm using pipenv all the time and 3-4 weeks ago it was normally working, I guess something has changed upstream

mpcogito commented 4 years ago

It may be that your module is too deeply nested, which seems to be a problem with pipenv. Try the code in this gist: https://gist.github.com/mpcogito/d6f2a2fb5595bf10e6109143071eee5b

k-jell commented 3 years ago

Is there any way this can be fixed while still using python-pipenv-activate? I'm not sure how to modify the code in the gist to do that.

lebensterben commented 3 years ago

@k-jell do that in shell

k-jell commented 3 years ago

@lebensterben Could you explain a bit further what I should do in shell? Setting the default-directory? Sorry if I'm missing something obvious here.

lebensterben commented 3 years ago

@k-jell

https://pipenv.pypa.io/en/latest/basics/#example-pipenv-workflow

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

github-actions[bot] commented 2 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

syl20bnr / spacemacs