You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many users find dependency-resolution hard.
My recommendations are usually (that ssb-project build does not cover):
Run poetry lock
Replace all dependencies from ^ to >=
I was wondering the right way to "recommend" this in the organization, and I think a warning during ssb-project build could be the best place to encourage right "signage".
Here is some example-code of what I mean.
importsubprocessdefcheck_deps_group(group: str) ->None:
deps=subprocess.check_output((f"grep -A 10 '\[{group}\]' pyproject.toml"), shell=True).decode("utf8").split("\n")
deps= [xforxindepsifxandnotx.startswith("[") and"build-backend"notinx]
forlineindeps:
vers_dep=line.split('"')[-2]
if">="notinvers_dep:
print(f"Dependency {line}, does not use recommended signage '>=', consider changing it?")
check_deps_group("tool.poetry.dependencies")
check_deps_group("tool.poetry.group.dev.dependencies")
Many users find dependency-resolution hard.
My recommendations are usually (that ssb-project build does not cover):
poetry lock
^
to>=
I was wondering the right way to "recommend" this in the organization, and I think a warning during ssb-project build could be the best place to encourage right "signage".
Here is some example-code of what I mean.
@arneso-ssb @krlono @rachelekren
The text was updated successfully, but these errors were encountered: