-
Notifications
You must be signed in to change notification settings - Fork 9
Style guide #67
base: dev
Are you sure you want to change the base?
Style guide #67
Conversation
How does this look, @suricactus? |
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 awesome!
You mentioned you want to publish 1.1 by the end of this week, but personally, I don't have enough time to change all the files to conform to the style guide. Therefore, I would suggest to enforce it after the release, as there are some nasty bugs already fixed on the dev branch/PRs.
About PEP8/PEP484 part, maybe after the changes you should put a link to a file, that is a good example of usage of these two PEPs. A line of code is worth a thousand words.
|
||
3. Implement type hints for all functions/methods ([PEP 484](https://www.python.org/dev/peps/pep-0484/)) | ||
|
||
4. Make sure your code passes all linting and test requirements before submitting your pull request. |
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.
4. Make sure your code passes all linting and test requirements before submitting your pull request. | |
4. Make sure your code passes all linting and test requirements before submitting your pull request, using `make lint` and there are no errors in the output. |
@@ -13,6 +13,10 @@ Whenever dev stabilizes a release is cut and we merge dev in to master. So maste | |||
It is possible that there may be small releases in quick succession, especially if they are nice improvements that do | |||
not require lots of updating. | |||
|
|||
## Contributing | |||
|
|||
Please read the [contributing guide](CONTRIBUTING.md) before submitting any pull requests. |
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.
Please read the [contributing guide](CONTRIBUTING.md) before submitting any pull requests. | |
Please read the [contributing guide](CONTRIBUTING.md) before submitting any bug reports or pull requests. |
Draft of style guide as per #65