BUG: read_csv with mixed bools and int sometimes reads 1 as a bool function.

[shubham11941140]

• closes BUG: read_csv converts NaN to 1.0 in certain circumstances #42808
• tests added / passed
• Ensure all linting tests pass, see here for how to run them
• whatsnew entry

The major issue is that the parser is reading 1 as a boolean expression and not as an integer.

So, making 2 different tests based on the data type of the input or return of a function can help split the parsing as two seperate entities.

Reference: #42944

[pep8speaks]

Hello @shubham11941140! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file pandas/tests/io/parser/test_na_values.py:

Line 594:1: E302 expected 2 blank lines, found 1
Line 597:41: E251 unexpected spaces around keyword / parameter equals
Line 597:43: E251 unexpected spaces around keyword / parameter equals
Line 598:56: E251 unexpected spaces around keyword / parameter equals
Line 598:58: E251 unexpected spaces around keyword / parameter equals
Line 600:1: E302 expected 2 blank lines, found 1
Line 603:55: E251 unexpected spaces around keyword / parameter equals
Line 603:57: E251 unexpected spaces around keyword / parameter equals
Line 607:1: E302 expected 2 blank lines, found 1
Line 610:41: E251 unexpected spaces around keyword / parameter equals
Line 610:43: E251 unexpected spaces around keyword / parameter equals
Line 611:50: E251 unexpected spaces around keyword / parameter equals
Line 611:52: E251 unexpected spaces around keyword / parameter equals

Comment last updated at 2021-08-23 13:40:10 UTC

[shubham11941140]

It mentions workflow requires approval, please do the same. I have also got few PEP 8 issues. Do I need to solve them?
The code is compiling correctly.

[mzeitlin11]

These changes look identical to #42944 with some changes like flipping if statements, test order, and removing comments?

[shubham11941140]

Ok I will write using reference.

[mzeitlin11]

Ok I will write using reference.

First, if you build off another PR, you should always reference it (otherwise looks like plagiarism). Also that PR is fine, so there is no reason for another one doing the same thing

[shubham11941140]

Could you suggest me how do I study with the codebase and then solve bugs?
Actually the issue is that I know how to solve bugs but I have no idea which files to modify and where to?

[shubham11941140]

The repo is huge due to which I am unable to find and pinpoint issues.

[mzeitlin11]

Closing this to not waste CI resources. Please do not copy code without credit in future.

[mzeitlin11]

Could you suggest me how do I study with the codebase and then solve bugs?
Actually the issue is that I know how to solve bugs but I have no idea which files to modify and where to?

https://pandas.pydata.org/docs/development/contributing.html will be helpful. Learning to use a debugger is the best way to learn how to solve bugs (since finding where to fix issues is the hardest part of solving them)