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

FILLMTR (SEPT17) [Python] #195

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

FILLMTR (SEPT17) [Python] #195

wants to merge 7 commits into from

Conversation

abhigyank
Copy link

@abhigyank abhigyank commented Oct 3, 2017

Fixes #189

  • Pull Request Title is of form Problem Code (Contest Code) [Language].
  • This problem already had an entry in this repository.
    • This solution is better than the one already in this repository.
  • This solution is prepared by me and not copied from anywhere else on the web.
  • I have added a copyright comment in my solution.
  • I have updated README.md file (in appropriate order).
  • I have read and followed Code Samples.
  • I understand that pull request will be closed if I failed to update it even once in a week.

@aashutoshrathi
Copy link
Member

Hi! Thanks for contributing to this repository.
Make sure you have checked points in PR correctly.

@abhigyank
Copy link
Author

Hey, I didn't understand what you posted. I haven't changed any of the files that are shown in the error.

@Monal5031 Monal5031 self-assigned this Oct 3, 2017
@Monal5031
Copy link
Member

@abhigyank Don't get frightened over such long messages those are auto-generated gitmate issues, from what I can see you need to resolve conflicts and update your repo, thats it. 😉

@abhigyank
Copy link
Author

@Monal5031 please review and merge.

print "no"

if __name__ == '__main__':
main()
Copy link
Member

Choose a reason for hiding this comment

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

Add a new line at the end.

Copy link
Author

Choose a reason for hiding this comment

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

@aashutoshrathi
Copy link
Member

@Monal5031 I request you not to delete, gitmate comments, as it will only raise coala issues.

@Monal5031
Copy link
Member

Monal5031 commented Oct 4, 2017

@aashutoshrathi I don't see travis in the check list, have you deactivated it?
Those gitmate messages are very much frightening and discouraging.
Also if you know gitmate raises issues on all the commits rather than the latest one, so each time a person updates a commit the same message of gitmate will be raised.

@Monal5031
Copy link
Member

@abhigyank Can make some changes and repush? Inorder to activate the travis build, so we can see what is causing the tests to fail.

@abhigyank
Copy link
Author

@Monal5031 What changes can I make? Maybe you can check the Travis logs or see in the next PR.

@Monal5031
Copy link
Member

@abhigyank You can add spaces around binary operator, like a=b as a = b

@abhigyank
Copy link
Author

@aashutoshrathi Maybe you should squash and merge now.

@Monal5031
Copy link
Member

Monal5031 commented Oct 5, 2017

@abhigyank Sorry for late reply but I can still see three issues in travis log for your PR.


|  26|    |-                    if(i[2]==1):

|    |  26|+                    if(i[2] == 1):

This one meaning you need to add space around binary opeator on line 26.
_________________________________________________________________

|  64|  64| 

|    |  65|+

|  65|  66| if __name__ == '__main__':

This one meaning you need to add a blank line before `if __name__ == '__main__':` on line 65.
__________________________________________________________________
|  64|  64| 

|  65|  65| if __name__ == '__main__':

|  66|  66|     main()

|  67|    |-    

This one meaning you have extra newline at end.

@Monal5031
Copy link
Member

ping @abhigyank Its been 5 days since this PR was last updated, please update it.

@abhigyank
Copy link
Author

@Monal5031 Check now please.

ans = 1
for i in range(n):
good.append('a')
good.append('a')
Copy link
Member

Choose a reason for hiding this comment

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

The code does not comply to PEP8.

Origin: PEP8Bear, Section: pep8.

The issue can be fixed by applying the following patch:

--- a/tmp/tmplt5sx928/2017/SEPT/SEPT17/FILLMTR/FILLMTR.py
+++ b/tmp/tmplt5sx928/2017/SEPT/SEPT17/FILLMTR/FILLMTR.py
@@ -62,7 +62,7 @@
         else:
             print "no"
 
-            
+
 if __name__ == '__main__':
     main()
     

good.append('a')
for i in range(q):
a = map(int, raw_input().split())
queries.append(a)
Copy link
Member

Choose a reason for hiding this comment

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

The code does not comply to PEP8.

Origin: PEP8Bear, Section: pep8.

The issue can be fixed by applying the following patch:

--- a/tmp/tmplt5sx928/2017/SEPT/SEPT17/FILLMTR/FILLMTR.py
+++ b/tmp/tmplt5sx928/2017/SEPT/SEPT17/FILLMTR/FILLMTR.py
@@ -65,4 +65,3 @@
             
 if __name__ == '__main__':
     main()
-    

@abhigyank
Copy link
Author

@aashutoshrathi @Monal5031 All tests passed. Squash and merge PR.

@abhigyank
Copy link
Author

Any reason why this hasn't been merged yet?

@Monal5031
Copy link
Member

@abhigyank Please resolve conflicts

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

Successfully merging this pull request may close these issues.

FILLMTR (SEPT17) [Python]
3 participants