crayons TypeError in core.py

I am having a special setup. I have a docker in which I create an emulated ARM rootfs using QEMU. Inside the emulated rootfs , I am going to create a virtual environment using pipenv which I can use later on my ARM target. What is happening now is that I am always receiving the following exception:

Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pipenv/cli.py", line 416, in install
    selective_upgrade=selective_upgrade,
  File "/usr/local/lib/python3.6/site-packages/pipenv/core.py", line 1789, in do_install
    skip_requirements=skip_requirements,
  File "/usr/local/lib/python3.6/site-packages/pipenv/core.py", line 641, in ensure_project
    crayons.green(shorten_path(path_to_python)),
TypeError: __str__ returned non-string (type NoneType)

As I traced the exception, I found out that problem here is that the python_version() method returns None in my case. Then as I use docker exec to run pipenv install, I think I am mixing different shell environment, therefore crayons.green cannot convert None type to string. My proposal would be simply just use str in all crayons e.g. crayons.green(str(python_version(path_to_python)))

[semiversus]

Here are two other issues addressing the same problem: #2650, #1969 . And as already mentioned something in detection of used python version is broken. For me adding --system (pipenv install --system) solved the issue.

[techalchemy]

Please fill out the issue template in full. The bug is not in crayons no matter how many times we see the same output. We have issue templates for a reason. I appreciate that everyone is taking time to troubleshoot, we also spent months (or years) building the library and if you can’t spend the time to fill out an issue template we can’t offer you any support.