vistir assumes it has chmod permissions, preventing pipenv lock
from completing
#4195
Labels
Category: Error Handling
Issue relates to error handling
Type: Bug 🐛
This issue is a bug.
Type: Vendored Dependencies
This issue affects vendored dependencies within pipenv.
Issue description
We are running pipenv on a shared drive that has permissions set at the share/mount level, not at the file level, which means that
chmod
will always fail.When running
pipenv lock
, a temporary file is created within the current directory. Near the end of the process, an unprotected chmod is attempted on that file, which results in an exception being thrown,Pipfile.lock
not being updated, and the temporary file not being deleted.The trouble is here:
pipenv/pipenv/vendor/vistir/contextmanagers.py
Line 237 in 5c01c68
Expected result
Pipfile.lock
updates without issue.Actual result
Steps to replicate
chmod
from succeeding in the current directory.pipenv lock
.Pipfile.lock
has not been updated, and a temporary file is left behind.Pipenv version:
'2018.11.26'
PEP 508 Information:
The text was updated successfully, but these errors were encountered: