-
Notifications
You must be signed in to change notification settings - Fork 64
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
Audit type hints and expose types via PEP561 #44
Comments
This comment has been minimized.
This comment has been minimized.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 120.0 DAI (120.0 USD @ $1.0/DAI) attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 3 months, 3 weeks ago. 1) dimitrivla has applied to start work (Funders only: approve worker | reject worker). I’ll view its contents, and review them. Look how it will progress. Learn more on the Gitcoin Issue Details page. 2) bhargavasomu has been approved to start work. I have already made a PR with completing the tasks mentioned, and waiting for a review. Learn more on the Gitcoin Issue Details page. |
@6ug can be approved to work on this (but please get a pull request opened within the next day) |
@6ug Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
1 similar comment
@6ug Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Hey @pipermerriam, Ryan from Gitcoin checking in. Looks like @6ug sent over a PR for you to check out! |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done @6ug due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
what does meaning of |
@6ug you're still clear to work on this, check your PR as I added a commit, rebased it and left a comment. |
@6ug Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
1 similar comment
@6ug Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done @6ug due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
As this issue has still been |
@pipermerriam I have made the sufficient changes in #48. Please review the PR and we could close this issue and bounty. |
@6ug Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Hey @pipermerriam and @Bhargavasomu, Ryan from Gitcoin here. Looks like 6ug has dropped out -- if you apply to the bounty @Bhargavasomu I'll approve you to work. From there, @pipermerriam can review #48 and close the bounty! Let me know if you have any questions :) 🌮 |
@ryan-shea I have applied at gitcoin page, so please approve whenever you get the chance. |
@Bhargavasomu just approved you :) |
@Bhargavasomu Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@gitcoinbot I have completed resolving the issue in PR #48, waiting for @pipermerriam to take a review on this. |
@gitcoinbot payment for this issue can be issued to @Bhargavasomu @Bhargavasomu thanks for doing this. |
@pipermerriam Glad everything went well, @Bhargavasomu once you formally submit work I can pay you out :) |
@ceresstation @gitcoinbot I am not able to find an option to submit work in gitcoin page. Maybe this is because the status says |
Sorry for the multiple pings @ceresstation , but could you please check the gitcoin page status, as I am not able to submit my work. Thankyou |
No problem @Bhargavasomu, looking into this, will pay you out using advanced payout instead if the solution turns out to take a bit more time :) |
@Bhargavasomu can u try now |
@owocki still I am not able to submit the work because the button is not highlighted. It is something like this. |
Hey @Bhargavasomu can you try again? Sorry! |
just put in a fix for this @Bhargavasomu |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 120.0 DAI (120.0 USD @ $1.0/DAI) has been submitted by: @ceresstation please take a look at the submitted work:
|
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 120.0 DAI (120.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @Bhargavasomu.
|
Hey @Bhargavasomu thanks for jumping on this so quickly after the other contributor dropped out, and thanks for bearing with us on the payout! |
@ceresstation thankyou. |
…n-docs Replace web3 reference with <MODULE_NAME>
What is wrong?
The library currently uses type hints, however they may be able to be tightened up.
In addition, PEP561 allows us to expose type hints from this library to other libraries which use it.
Definition of done?
mypy
to the latest stable released version.mypy
run in CI to the following.Usage of
type: ignore
(silencing the type checker) is minimized and there's a reasonable explanation for its usageUpdate the
setup.py
to expose this data to other libraries as was done here: Enable discovery of type hints as per PEP561 eth-typing#10Stretch goals
When this issue is done, stretch goals can be applied (and individually get funded) to tighten type support to qualify:
mypy --strict --follow-imports=silent --ignore-missing-imports --no-strict-optional -p eth_keys
Do what was done in ethereum/eth-typing#10 to allow this data to be exposed when this library is installed as a package.
The text was updated successfully, but these errors were encountered: