Skip to content
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

Closed
pipermerriam opened this issue Oct 17, 2018 · 35 comments · Fixed by #48
Closed

Audit type hints and expose types via PEP561 #44

pipermerriam opened this issue Oct 17, 2018 · 35 comments · Fixed by #48

Comments

@pipermerriam
Copy link
Member

pipermerriam commented Oct 17, 2018

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?

  • Update mypy to the latest stable released version.
  • Update the mypy run in CI to the following.
mypy --follow-imports=silent --warn-unused-ignores --ignore-missing-imports --no-strict-optional --check-untyped-defs --disallow-incomplete-defs --disallow-untyped-defs --disallow-any-generics -p eth_keys`

Stretch goals

When this issue is done, stretch goals can be applied (and individually get funded) to tighten type support to qualify:

  1. 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.

@pipermerriam pipermerriam changed the title Rudit type hints and expose types via PEP561 Audit type hints and expose types via PEP561 Oct 17, 2018
@carver

This comment has been minimized.

@gitcoinbot
Copy link

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.

@gitcoinbot
Copy link

gitcoinbot commented Oct 17, 2018

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.
Please review their action plans below:

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.

@pipermerriam
Copy link
Member Author

@6ug can be approved to work on this (but please get a pull request opened within the next day)

@gitcoinbot
Copy link

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

1 similar comment
@gitcoinbot
Copy link

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@rmshea
Copy link

rmshea commented Oct 25, 2018

Hey @pipermerriam, Ryan from Gitcoin checking in. Looks like @6ug sent over a PR for you to check out!

@gitcoinbot
Copy link

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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@6ug
Copy link

6ug commented Oct 25, 2018

what does meaning of Escalated for Abandonment of Bounty, should I work for this issue?

@pipermerriam
Copy link
Member Author

@6ug you're still clear to work on this, check your PR as I added a commit, rebased it and left a comment.

@gitcoinbot
Copy link

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

1 similar comment
@gitcoinbot
Copy link

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot
Copy link

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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@Bhargavasomu
Copy link
Contributor

As this issue has still been unresolved, I would like to work on this. @pipermerriam do I have the permission to go for it? @gitcoinbot could you please reopen this issue?

@Bhargavasomu
Copy link
Contributor

Bhargavasomu commented Nov 4, 2018

@pipermerriam I have made the sufficient changes in #48. Please review the PR and we could close this issue and bounty.

@gitcoinbot
Copy link

@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!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@rmshea
Copy link

rmshea commented Nov 8, 2018

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 :) 🌮

@Bhargavasomu
Copy link
Contributor

@ryan-shea I have applied at gitcoin page, so please approve whenever you get the chance.

@spm32
Copy link

spm32 commented Nov 8, 2018

@Bhargavasomu just approved you :)

@gitcoinbot
Copy link

@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!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@Bhargavasomu
Copy link
Contributor

@gitcoinbot I have completed resolving the issue in PR #48, waiting for @pipermerriam to take a review on this.

@pipermerriam
Copy link
Member Author

@gitcoinbot payment for this issue can be issued to @Bhargavasomu

@Bhargavasomu thanks for doing this.

@spm32
Copy link

spm32 commented Nov 12, 2018

@pipermerriam Glad everything went well, @Bhargavasomu once you formally submit work I can pay you out :)

@Bhargavasomu
Copy link
Contributor

@ceresstation @gitcoinbot I am not able to find an option to submit work in gitcoin page. Maybe this is because the status says Warned for Abandonment of Bounty. Could you please look into it and let me know what to do?

@Bhargavasomu
Copy link
Contributor

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

@spm32
Copy link

spm32 commented Nov 14, 2018

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 :)

@owocki
Copy link

owocki commented Nov 14, 2018

@Bhargavasomu can u try now

@Bhargavasomu
Copy link
Contributor

@owocki still I am not able to submit the work because the button is not highlighted. It is something like this.
screenshot from 2018-11-14 14-35-38

@spm32
Copy link

spm32 commented Nov 14, 2018

Hey @Bhargavasomu can you try again? Sorry!

@owocki
Copy link

owocki commented Nov 14, 2018

just put in a fix for this @Bhargavasomu

@gitcoinbot
Copy link

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:

  1. @bhargavasomu

@ceresstation please take a look at the submitted work:


@gitcoinbot
Copy link

⚡️ A *Fast Response* Kudos has been sent to @Bhargavasomu for this issue from @ceresstation. ⚡️

Nice work @Bhargavasomu!
Your Kudos has automatically been sent in the ETH address we have on file.

@gitcoinbot
Copy link

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.

@spm32
Copy link

spm32 commented Nov 15, 2018

Hey @Bhargavasomu thanks for jumping on this so quickly after the other contributor dropped out, and thanks for bearing with us on the payout!

@Bhargavasomu
Copy link
Contributor

@ceresstation thankyou.

pacrob pushed a commit to pacrob/eth-keys that referenced this issue Dec 20, 2023
…n-docs

Replace web3 reference with <MODULE_NAME>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants