Skip to content
This repository has been archived by the owner on Nov 9, 2021. It is now read-only.

Style guide #67

Draft
wants to merge 2 commits into
base: dev
Choose a base branch
from
Draft

Style guide #67

wants to merge 2 commits into from

Conversation

kbgg
Copy link
Owner

@kbgg kbgg commented Jul 10, 2019

Draft of style guide as per #65

@kbgg
Copy link
Owner Author

kbgg commented Jul 10, 2019

How does this look, @suricactus?

Copy link
Contributor

@suricactus suricactus left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants