Skip to content

Conversation

@cscheid
Copy link
Collaborator

@cscheid cscheid commented May 8, 2024

Closes #9618.

@cscheid
Copy link
Collaborator Author

cscheid commented May 8, 2024

@cderv I'll need some help from you in setting up those Pipfile and Pipfile.lock files. I changed the Pipfile but my attempt to PIPENV_IGNORE_VIRTUALENVS=1 pipenv install jupyter_cache ended up with a totally different Pipfile.lock.

@cscheid cscheid requested a review from cderv May 8, 2024 20:10
@cderv
Copy link
Collaborator

cderv commented May 13, 2024

ended up with a totally different Pipfile.lock.

I don't know how different it was. Running pipenv install will re-lock from the PipFile - this means that everything will be resolved again to latest as we don't pinned version that much (using "*" for all our deps).

So the Pipfile.lock will end up different as everything could be updated. Running pipenv update jupyter-cache can have less impact and it should only tweak the dependencies from the package and do not resolved the rest.

I did that here, let's see if this works ok. There could be some OS tweak unfortunately as Python dependencies management is bad cross-OS. I'll handle windows, but you should check on Mac maybe

@cscheid cscheid merged commit 5c649d9 into main May 13, 2024
@cscheid cscheid deleted the bugfix/9618 branch May 13, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error when accessing the jupyter cache

3 participants