Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pipenv shell error

See original GitHub issue

After I install package by pipenv in Windows and run following command: pipenv shell. Then it come up with AttributeError. How could I fix problem.

Expected result

Go into virtualenv

Actual result

Traceback (most recent call last):
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\core.py", line 2142, in do_shell
    c = pexpect.spawn(
AttributeError: module 'pexpect' has no attribute 'spawn'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\users\ricky\anaconda3\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\ricky\anaconda3\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\ricky\Anaconda3\Scripts\pipenv.exe\__main__.py", line 9, in <module>
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\vendor\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\vendor\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\vendor\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\vendor\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\vendor\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\cli.py", line 572, in shell
    three=three, python=python, fancy=fancy, shell_args=shell_args
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\core.py", line 2156, in do_shell
    pew.workon_cmd([workon_name])
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\patched\pew\pew.py", line 379, in workon_cmd
    shell(env, cwd=project_dir)
  File "c:\users\ricky\anaconda3\lib\site-packages\pipenv\patched\pew\pew.py", line 206, in shell
    shell_name = Path(shell).stem
  File "c:\users\ricky\anaconda3\lib\pathlib.py", line 979, in __new__
    self = cls._from_parts(args, init=False)
  File "c:\users\ricky\anaconda3\lib\pathlib.py", line 654, in _from_parts
    drv, root, parts = self._parse_args(args)
  File "c:\users\ricky\anaconda3\lib\pathlib.py", line 638, in _parse_args
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Issue Analytics

State:
Created 5 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

2reactions

uranusjrcommented, Apr 12, 2018

Just use pipenv run.

2reactions

uranusjrcommented, Apr 12, 2018

@feakuru Unfortunately Msys is not supported at the moment. There are no plan to add support either unless there are new contributors interested in it.

Top Results From Across the Web

pipenv shell, does not activate the virtual environment

Try doing this: pip uninstall pipenv. this will uninstall existing pipenv after doing that re-install pipenv by doing this:

Frequently Encountered Pipenv Problems - Read the Docs

This is usually a result of mixing Pipenv with system packages. We strongly recommend installing Pipenv in an isolated environment. Uninstall all existing ......

pipenv create virtual env error · Issue #5101 - GitHub

Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.

Common Pipenv Errors - Towards Data Science

A collection of Pipenv errors and their solutions. ... The command pipenv shell points to a virtual environment on your computer.

Bug #1970106 “Running “pipenv shell” fails with AttributeError”

I recently upgraded from Ubuntu 20.04 to 22.04 Running pipenv shell to create a virtual env results in the following and no environment...