Skip to content

Use fallback_version if SCM isn't found #549

@CharlesB2

Description

@CharlesB2

I'm in some situation (testing my package in Docker) where git isn't available, and thought I could just use fallback_version argument, but it turns out I still get an exception OSError: 'git' was not found.

I found I can overcome this by defining the SETUPTOOLS_SCM_PRETEND_VERSION environment variable, but I thought it would be easier to use fallback_version in this case as well?

I'm not sure I understood the different cases where one should use SETUPTOOLS_SCM_PRETEND_VERSION or fallback_version?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions