As of end-Nov 2018, creating a
lock file takes really long time, and this
TIMEOUT error (and
lock file is NOT created)
There are two ways to handle this.
pipenv install --skip-lockThis will, as the parameter suggests, will not create the lock file, this
avoidingdelaying the issue.
- Now you can create the
pipenv lock, but that would run into the same issue. So setup
PIPENV_TIMEOUTenvironment variable before running the
pipenv lockcommand. The value is in seconds. So for 3 minutes, set it to 180 (default is 120). Guessing how much to set it to is tricky. So if you are unsure, set it to some really high value like 10000
See the output from
If the test cases have
print() statements, you see those, only in case of failure.
But sometime, you want to see they unconditionally (i.e. even when the tests pass)
The way to do this is use
-s option. This option disables "per test capturing".
Read the docs
%(asctime)s %(levelname)-5.5s [%(name)s:%(lineno)s][%(threadName)s]
(Reference: Pyramid Logging tutorial)