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

Refresh PR #2216 #3881

Open
wants to merge 18 commits into
base: master
from
Open

Refresh PR #2216 #3881

wants to merge 18 commits into from

Conversation

@crazazy
Copy link

@crazazy crazazy commented Nov 12, 2020

Describe your change:

See #2216

  • Add an algorithm?
  • Fix a bug or typo in an existing algorithm?
  • Documentation change?

Checklist:

  • I have read CONTRIBUTING.md.
  • This pull request is all my own work -- I have not plagiarized.
  • I know that pull requests will not be merged if they fail the automated tests.
  • This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
  • All new Python files are placed inside an existing directory.
  • All filenames are in all lowercase characters with no spaces or dashes.
  • All functions and variable names follow Python naming conventions.
  • All function parameters and return values are annotated with Python type hints.
  • All functions have doctests that pass the automated testing.
  • All new algorithms have a URL in its comments that points to Wikipedia or other similar explanation.
  • If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.
crazazy and others added 11 commits Jul 19, 2020
It's been a while since I worked with typed python, forgive me ok?
I am not sure it the calculate_chain doctest works, since they are
testing the side effects of the function, we will see what CI thinks of
it
noone gave a good reason on why to remove it, and since this file is
executable anyway (and thus easier to run for me)
doctests reset the environment after each function evaluation, so we
can't use doctests to inspect side effects of void functions
@crazazy crazazy requested review from dhruvmanila and Kush1101 as code owners Nov 12, 2020
crazazy and others added 6 commits Nov 12, 2020
… master

# Conflicts:
#	project_euler/problem_014/sol3.py
github-actions github-actions
Turns out that we don't do any doctests here anymore, we just write our
oWN FRAMEWORK NOW DO WE?!
@xcodz-dot
Copy link
Contributor

@xcodz-dot xcodz-dot commented Nov 13, 2020

run the following commands in order:

  • clone your forked repository locally
  • change directory to its root
  • run pip install pre-commit
  • run pre-commit run --all-files twice

commit and push the changes to your fork.

@crazazy
Copy link
Author

@crazazy crazazy commented Nov 13, 2020

Consider it fixed

@xcodz-dot
Copy link
Contributor

@xcodz-dot xcodz-dot commented Nov 16, 2020

@dhruvmanila, please check this.

@53jk1
53jk1 approved these changes Nov 19, 2020
@dhruvmanila
Copy link
Member

@dhruvmanila dhruvmanila commented Nov 20, 2020

Thank you for your contribution but currently, we're not accepting solutions to problems that already exist. Try to solve a problem which is not present in the directory and submit a PR for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants
You can’t perform that action at this time.