Skip to content

Fix handling of default_install_tag #372

@zooba

Description

@zooba

As noticed in these logs, install.default_install_tag is overridden by the default configuration to 3, rather than matching the value of default_tag. This means that a user who has overridden their default_tag to (say) 3.13 can't use py install default properly, because it will infer that to mean 3 and so will match any existing 3.x install rather than the intended default.

We either need to remove the default value for install.default_install_tag (so that it uses default_tag instead) or change when it's used (e.g. not for literal py install default but keep it for other default installs).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions