-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: 'NoneType' object is not iterable #3265
Comments
Hey @sunbearc22, We did a quick check and this issue looks very darn similar to
This could be a coincidence, but if any of these issues solves your problem then I did a good job 😄 If not, the maintainers will get to this issue shortly. Cheers, |
@techalchemy I believe the fixed master has not been released yet. I have just tried uninstalling and reinstalling pipenv, and pipenv is still giving the same error msg. May I know when the fix will surely be release? Cheers. Edit:
|
No worries, the actual fix will be released shortly (in the process of a few more fixes before we can release) -- sorry again for the trouble, I know a lot of folks are relying on pipenv for day to day processes |
Hello @techalchemy! Thanks for your work on this tool! I am running |
Do you happen to know if a fix will be available through homebrew in the near future, or can I try and rollback to 2018.10.13 with homebrew? I'm new to Python and my entire workflow goes through pipenv. |
Release is up on pypi. No idea about homebrew :( |
Today's release did it for me. Thanks! |
Issue description
For
pipenv
version 2018.11.14, the creation ofPipfile
is constantly returningTypeError: 'NoneType' object is not iterable
. I got this error when I issued commandspipenv install -e .
orpipenv --python 3.6.7
orpipenv install numpy
. For the latter, the creation of the Virtualenv location was completed. What should I do next?Expected result
Successful creation of Pipefile and Pipfile.lock and the installation of required package in virtual environment.
Actual result
The text was updated successfully, but these errors were encountered: