Skip to content

Conversation

StephenRobin
Copy link

Our build system sets the package version number via an environment variable.

When developers are building locally (eg when doing a uv sync) the environment variable will not be set and the build fails. This is inconvenient and we'd rather it just fell back to some default value like 0.0.1.dev0+local)

Our build system sets the package version number via an environment variable.

When developers are building locally (eg when doing a `uv sync`) the
environment variable will not be set and the build fails. This is inconvenient
and we'd rather it just fell back to some default value like 0.0.1.dev0+local)
@StephenRobin
Copy link
Author

Hi @ofek, is there anything I can do to help progress this PR?

@mansoor2016
Copy link

Our build system sets the package version number via an environment variable.

When developers are building locally (eg when doing a uv sync) the environment variable will not be set and the build fails. This is inconvenient and we'd rather it just fell back to some default value like 0.0.1.dev0+local)

Without this patch, env var versioning is useless, it will not work for local development without hacks.

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.

2 participants