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
Currently if a build is performed using one package manager (eg Pipenv), and then a subsequent build is performed using a different package manager (eg pip), the build cache is not cleared, resulting in leftover files and packages (such as the Pipenv installation still being present).
edmorley
changed the title
The cache isn't cleared if a project switches to a different package manager (eg Pipenv to pip)
The cache isn't cleared when switching to a different package manager (eg Pipenv to pip)
Oct 30, 2024
edmorley
changed the title
The cache isn't cleared when switching to a different package manager (eg Pipenv to pip)
The cache isn't cleared when switching to a different package manager
Oct 30, 2024
edmorley
changed the title
The cache isn't cleared when switching to a different package manager
Clear the cache when switching to a different package manager
Oct 30, 2024
Currently if a build is performed using one package manager (eg Pipenv), and then a subsequent build is performed using a different package manager (eg pip), the build cache is not cleared, resulting in leftover files and packages (such as the Pipenv installation still being present).
This can be seen in these recently added tests:
heroku-buildpack-python/spec/hatchet/pip_spec.rb
Lines 104 to 126 in dba9b86
heroku-buildpack-python/spec/hatchet/pipenv_spec.rb
Lines 286 to 311 in dba9b86
Fixing this blocks adding support for Poetry in #796, since there will be a number of apps that may switch package manager to try out Poetry.
The text was updated successfully, but these errors were encountered: