This requires both a changelog and an automatic git tagging feature.
The issue here is that setuptools_scm will only follow fully semantic updating if on a release- branch (link), even when using its built-in semantic versioning setup, otherwise it will always append devX to the branch version. I've yet to find any way to override this behavior.
Getting this working properly would allow the package to be imported via pip following the standard scheme in use elsewhere, preventing the need to install manually via git when using, e.g., policyengine-us.
MaxGhenis
commented
1 week ago
This requires both a changelog and an automatic git tagging feature.
The issue here is that
setuptools_scmwill only follow fully semantic updating if on arelease-branch (link), even when using its built-in semantic versioning setup, otherwise it will always appenddevXto the branch version. I've yet to find any way to override this behavior.Getting this working properly would allow the package to be imported via
pipfollowing the standard scheme in use elsewhere, preventing the need to install manually via git when using, e.g.,policyengine-us.