Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Python install scratch directory from .cache -> .temp #9756

Merged
merged 1 commit into from
Dec 10, 2024

Conversation

zanieb
Copy link
Member

@zanieb zanieb commented Dec 10, 2024

Addressing the confusion in #9749

@zanieb zanieb added the enhancement New feature or improvement to existing functionality label Dec 10, 2024
@zanieb zanieb requested a review from charliermarsh December 10, 2024 02:53
@konstin
Copy link
Member

konstin commented Dec 10, 2024

What about .temp? This makes it clear to the user that they can safely remove the directory if one remains around.

@zanieb zanieb force-pushed the zb/python-install-scratch branch from 6bacb8e to d19d22e Compare December 10, 2024 14:29
@zanieb zanieb changed the title Rename Python install scratch directory from .cache -> .scratch Rename Python install scratch directory from .cache -> .temp Dec 10, 2024
@zanieb zanieb enabled auto-merge (squash) December 10, 2024 14:30
@zanieb zanieb merged commit cb03858 into main Dec 10, 2024
64 checks passed
@zanieb zanieb deleted the zb/python-install-scratch branch December 10, 2024 14:41
self.root.join(".cache")
/// Return the location of the scratch directory for managed Python installations.
pub fn scratch(&self) -> PathBuf {
self.root.join(".temp")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the rename here is now showing a warning:

WARN Ignoring malformed managed Python entry:
    Failed to parse Python installation key `.cache`: not enough `-`-separated values

Can you look for the usages? I think we exclude files that match this name somewhere, and now .cache exists for users but won't be skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improvement to existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants