Skip to content

Conversation

@gribok
Copy link
Contributor

@gribok gribok commented Mar 26, 2020

Based on #169, provides first version of contrib guide.

@Kilo59 Kilo59 added the documentation Improvements or additions to documentation label Mar 26, 2020

Please follow [PEP8](https://www.python.org/dev/peps/pep-0008/) guide.
See [Running Test](./README.md#running-tests) and [Linting](./README.md#linting) for further instructions.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we add a step here about running the formatter?
pipenv run fmt or make fmt or black . -l 120

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for feedback. Added make ftm to styleguide section.

@gribok gribok mentioned this pull request Mar 29, 2020
@gribok
Copy link
Contributor Author

gribok commented Mar 29, 2020

Some points to discuss? :-)

Copy link
Collaborator

@Kilo59 Kilo59 left a comment

Choose a reason for hiding this comment

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

The contribution sections looks good 😄.
A couple of issues with the coverage changes. IMO they should also be part of a separate PR.

install:
- "pip install pipenv"
- "pipenv install --dev --skip-lock"
- "pipenv install coveralls"
Copy link
Collaborator

Choose a reason for hiding this comment

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

IMO this coveralls stuff should be a totally separate PR but...

You shouldn't use pipenv install this dependency here.

  1. Either add it to the Pipfile so that it gets installed along with the dev dependencies
  2. install it directly with pip in the first install step. pip install pipenv coveralls

Comment on lines +11 to +13
pytest-cov="*"
pylint = "*"
coveralls = "*"
Copy link
Collaborator

@Kilo59 Kilo59 Mar 29, 2020

Choose a reason for hiding this comment

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

Updates to the Pipfile should always be accompanied by a new Pipfile.lock
Run pipenv lock to regenerate a new lockfile.
However, if you are on a windows machine it may not generate the correct dependencies for a deployment. If so let me know and I would be happy to generate it for you,

@Kilo59
Copy link
Collaborator

Kilo59 commented Mar 30, 2020

@gribok Can I remove the coverage stuff from this branch and merge it?

@gribok
Copy link
Contributor Author

gribok commented Mar 30, 2020

I am going to close the PR, seperate the changes for #169 and #207 in two branches and create new PRs based on mentioned issues.

@gribok gribok closed this Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants