Replies: 5 comments 2 replies
|
I use: |
|
I made the test with below patch: --- a/pyproject.toml
+++ b/pyproject.toml
@@ -55,5 +55,5 @@
[tool.poetry-plugin-tweak-dependencies-version]
default = "present"
[build-system]
-requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning", "poetry-plugin-drop-python-upper-constraint", "poetry-plugin-tweak-dependencies-version"]
+requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning"]
build-backend = "poetry.core.masonry.api"And looks like both modules indeed are not needed and was able to build module without any issues. + PBR_VERSION=1.5.2
+ PDM_BUILD_SCM_VERSION=1.5.2
+ SETUPTOOLS_SCM_PRETEND_VERSION=1.5.2
+ /usr/bin/python3 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
* Building wheel...
Successfully built poetry_plugin_tweak_dependencies_version-0.1.0-py3-none-any.whlPlease let me know if you want this patch as PR. |
|
Ha .. version is wrong. |
Issue is that on top of what is possible to obtain from VCS is should be possible to inject version from some env variable when module is build from autogenerated from git tag tar ball which does not contain VCS metadata. |
|
|
Uh oh!
There was an error while loading. Please reload this page.
Looks like to build
poetry-plugin-tweak-dependencies-versionI must have already build and installedpoetry-plugin-tweak-dependencies-versionwhich additionally requirespoetry-plugin-drop-python-upper-constraintand .. to build
poetry-plugin-drop-python-upper-constraintI must have build and installedpoetry-plugin-tweak-dependencies-version.馃
All reactions