-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change poe tasks naming #604
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks okay, but @approxit 's comments still stand
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I can see poetry.lock
in repo, which currently is not included in VCS across SDK libraries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
It always has .lock so we can keep it as for now |
b944572
to
3c704f7
Compare
Initial gole of this PR was to bump goth's dependencies so it is possible to use
click>=8
(dependency ofmitmproxy
andblack
). Unfortunately, goth yields unexpected errors when usingmitmproxy>=7
. I ended up with bumping versions slightly. As a resultclick>=8
is still not supported.What has been done:
.flake8
to pyproject.toml (this required flak8 bump to^5
)^6
tool.poe.tasks
so they match other golemfactory python project (including github workflows configurations)mypy
to newer version -poe checks_typing
yields the same warning on both versionsmitmproxy
more: Bump mitmproxy version to ^8 #605yapapi compatibility test
golemfactory/yapapi#1093
Edit: After yapapi compatibility test we decided to not upgrade
mitmproxy
at all and only merge changes to poe tasks and dev packages upgrade