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 5, 2022. It is now read-only.
The pip support checks whether pip is installed (runs 'which pip'), and does not create the pip bucket if pip is not yet found. However this means that when using a bootstrap script that installs pip and then installs a requirements file then those pip requirements will never use the cache. As a workaround pip has to be installed in a separate bootstrap script first.
This might make some sense in the 'autodetect' mode, but if the pip bucket is explicitly enabled (config.cache.enable :pip) it might make more sense to avoid the 'which pip' test and always create the bucket.
The text was updated successfully, but these errors were encountered:
Hey, sorry for the silence here but this project is looking for maintainers 😅
As per #193, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋
The pip support checks whether pip is installed (runs 'which pip'), and does not create the pip bucket if pip is not yet found. However this means that when using a bootstrap script that installs pip and then installs a requirements file then those pip requirements will never use the cache. As a workaround pip has to be installed in a separate bootstrap script first.
This might make some sense in the 'autodetect' mode, but if the pip bucket is explicitly enabled (config.cache.enable :pip) it might make more sense to avoid the 'which pip' test and always create the bucket.
The text was updated successfully, but these errors were encountered: