You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2017. It is now read-only.
Command fails because lib already contains the dependencies. Wouldn't it be better to specify something like pip install --upgrade -r requirements.txt in the README?
The text was updated successfully, but these errors were encountered:
I do see some warnings, but they are just that, warnings. Don't see a need to force replacement given we're pinning dependencies.
I agree it's strange to pre-vendor the dependencies. The reason we do it for these projects is they are used in quickstarts where the repo is directly downloaded, and where we say "just clone then do appcfg.py update", and people don't necessarily see the README.
Command fails because lib already contains the dependencies. Wouldn't it be better to specify something like
pip install --upgrade -r requirements.txt
in the README?The text was updated successfully, but these errors were encountered: