AttributeError: 'NoneType' object has no attribute 'pythons' when creating new pipfile #3439
Comments
uranusjr
added
the
Type: Vendored Dependencies
|
Looks like a bug in pythonfinders. |
|
Hi, thanks for the awesome tool. Looks like I ran into the same problem. Is there an earlier version pf pipenv that can create new packages on Unix systems? |
|
I am encountering the same issue here I think, using pyenv 1.2.9 (via homebrew) and pipenv 2018.11.26 (via homebrew) on OSX 10.14.3. I have a difference in that I was using already setup venv (using pyenv). `>$ pipenv --support $ pipenv --supportPipenv version: Pipenv location: Python location: Python installations found: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Interestingly I spot that it is looking at a python with (invalid) name "venv372" which is not what I named my venv using pyenv... although version 3.7.2 would be correct. |
- Update gitignore entries for mypy config - Update release task to add version after bumping but before release - Fixes #3326 (going forward at least) - Split out patching from vendoring so it can be done as a separate step if needed - Update patches to account for updated packages - Fixes #3432 - Fixes #2757 - Fixes #3305 - Fixes #2914 - Fixes #3439 - Fixes #3422 - Fixes #3378 - Fixes #3376 - Fixes #3315 Signed-off-by: Dan Ryan <dan@danryan.co>
|
After a little more playing, I have found that it doesn't work either when using `>$ pipenv install ✔ Successfully created virtual environment! During handling of the above exception, another exception occurred: Traceback (most recent call last): What strikes me as strange about this, and also my previous error posted above, is that Sorry if that sounds confusing. |
|
Sorry I have one more update: I changed the pipenv command and managed to get things working again! What I was doing before: |
|
Had a similar issue and the problem for me was that macOS had created a rm /Users/YOUR_USER_NAME/.pyenv/versions/.DS_Store |
|
@WillAyd Oh man, I did have a This output looks different from the original issue, but there sure seems to be something fishy going on with creating virtualenvs with pipenv. It's been busted for me since last year :( |
|
In my case, I had a zip file in the Removing the zip file(s) means it works. |
|
In case anybody winds up here from Google, I had this issue and the reason was a symlink in my It appears that plonking anything other than exactly what pyenv expects in the |
|
I ran into this even though my p.s. the way I figured out something was wrong with that particular version (it wasn't the version I was trying to use btw) was that the |
|
I ran into the same issue with the I found a workaround that helped me:
I'm still not sure what was the problem but this helped me get the work done |
|
Further explanation of @dammitjim 's solution. For me, the issue was due to a dead symlink in my The culprit symlink:
|
|
I think the problem started for me when I added the virtualenv plugin to pyenv. It created symlinks in the versions folder. |
|
getting this error below when running:
where python 3.7.4 is the global python set so by pyenv from the above it sounds like this should either have already been resolved, or is due to symlinks in the .pyenv/versions/X.X.X/bin/ directory I re-installed everything, i.e. pyenv, virtualenv, and pipenv today and the issue is still coming up. So it's not due to an older version. got it to work by setting the python version explicitly by path: pipenv --python ~/.pyenv/versions/3.7.4/bin/python3.7 |
|
The vendored I got things working by patching |
|
I had the same issue on linux. |
|
to those struggling with this issue -- can you confirm whether it is resolved using the prelease version? You can install the prerelease via |
|
@techalchemy It seems to resolve the issue for me. Thanks for a lot for your work, looks like I can finally move away from those On a related note when is the next release (or just the tentative dates)? |
|
@techalchemy I seem to have an issue with namespace packages |
|
I fixed the problem with the following: My errors were: |
Issue description
I tried to run
pipenv install --verboseand it failed.Expected result
I expected a virtualenv to be set up, a pipfile to be created, and no errors to pop up.
Actual result (ran with
--verbose)Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
pipenv install --verboseon macOS with pyenv installed.$ pipenv --support
Pipenv version:
'2018.11.26'Pipenv location:
'/usr/local/Cellar/pipenv/2018.11.26/libexec/lib/python3.7/site-packages/pipenv'Python location:
'/usr/local/Cellar/pipenv/2018.11.26/libexec/bin/python3.7'Python installations found:
The text was updated successfully, but these errors were encountered: