BrandonFors/pandas-github-issues huggingface dataset:
TST: Solution to doctest error in _parse_latex_header_span
State: closed

The following commit fixes the doctext in _parse_latex_header_span. Solves issue #42673

- [X] closes #42673 


Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: Docs

Comments:
> Thanks! If you want, you can add the file here, so it's validated in the CI, and no more errors are introduced:
> 
> https://github.com/pandas-dev/pandas/blob/c1aea793e03f11b587fbda833b2f5ad06c4bbced/ci/code_checks.sh#L123

Done. Please check the latest commit.
Can someone please help me in understanding why one check is failing? It looked like there is some conda virtual environment issue. I don't know if this information is relevant, but I've followed this section (https://pandas.pydata.org/docs/development/contributing_environment.html#creating-a-python-environment-pip) to setup a local environment. 
Sorry @aneesh98, my fault. You fixed one of the examples in that file, but there are couple more that are still failing. You can remove the file you added to `ci/code_checks.sh` (or fix those two cases). If you fix the other cases in the file, let them know in #42674.

Thanks!
Hi @datapythonista. For fixing those 2 cases I'll have to make 2 different pull requests right?. Also am I supposed to put some message on #42674 before fixing it, because I guess someone else has already taken up the issue.
Thanks.
> Hi @datapythonista. For fixing those 2 cases I'll have to make 2 different pull requests right?. Also am I supposed to put some message on #42674 before fixing it, because I guess someone else has already taken up the issue.
> Thanks.

Large PRs are usually discouraged. Since it's a waste of time to have to review a very big PR every time there is a new update to it. But I think in this case the PR will still be quite small and focused, so all in the same is surely ok.

It happens very often that people assign issues to themselves, and then they don't have the time to work on them. Since those are small fixes, I think several days without activity tells that this is quite likely to be the case. But it's surely polite to write a comment in the issue, and ask if there has been any progress, and if it's ok that you continue the work on it.
> > Hi @datapythonista. For fixing those 2 cases I'll have to make 2 different pull requests right?. Also am I supposed to put some message on #42674 before fixing it, because I guess someone else has already taken up the issue.
> > Thanks.
> 
> Large PRs are usually discouraged. Since it's a waste of time to have to review a very big PR every time there is a new update to it. But I think in this case the PR will still be quite small and focused, so all in the same is surely ok.
> 
> It happens very often that people assign issues to themselves, and then they don't have the time to work on them. Since those are small fixes, I think several days without activity tells that this is quite likely to be the case. But it's surely polite to write a comment in the issue, and ask if there has been any progress, and if it's ok that you continue the work on it.

Okay. Thanks. 
thanks @aneesh98
Regression in merge_asof raising KeyError when at least one by columnis in index
State: closed

- [x] xref #34488 
- [x] closes https://github.com/pandas-dev/pandas/issues/29130
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

This time correctly. This should cover the index case missed in the past

Labels:
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Regression
description: Functionality that used to work in a prior pandas version

Comments:
thanks @phofl 
@meeseeksdev backport 1.3.x
Something went wrong ... Please have  a look at my logs.
Revert "Regression in merge_asof raising KeyError when at least one by column is in index
State: closed

I am really sorry for this.

I messed up my acces token and accidentially pushed to master. Not sure how this could happen :(

If someone has a better idea than simply reverting we can close this

cc @pandas-dev/pandas-core 


Labels:

Comments:
I did something similar about 6 months ago. No worries. We reverted that.
Thanks for the quick help, merging this then

Comforting, that I am not the only one this happened to 
yep no problemo!
REGR: ValueError raised when both prefix and names are set to None
State: closed

- [ ] closes #42387 
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:
name: Regression
description: Functionality that used to work in a prior pandas version
name: IO CSV
description: read_csv, to_csv

Comments:
Hello @lithomas1! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:





There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2021-07-29 23:28:33 UTC
lgtm. @phofl if you can give a once over.
BUG: ArrayManager construction unwanted copy
State: closed

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

This is also going to be necessary in order to allow round-tripping DataFrame(arr).values as a view on arr

Labels:

Comments:
might warrant a whatsnew note in an array manager section (pls add in a follow on)
Fixed bug: Dataframe.sort_values not raising ValueError for ascending-incompatible value and Series.sort_values raising ValueError for int value
State: closed

- [x] closes #41634
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry


Labels:
name: Error Reporting
description: Incorrect or improved errors from pandas

Comments:
Apologies for any issues/mistakes. This is my first ever pull request to open source community.
**Thanks for the review @phofl.**
All the comments are addressed.
Hi @attack68, what are your thoughts on previous comment of mine? if it looks good, is it good to merge?
thanks @gaikwadrahul20 
Thanks a lot @jreback.
Bug in concat creating invalid MultiIndex
State: closed

- [x] closes #42651
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

I am checking the levels here to make it clear, what caused the issue previously. 

Labels:
name: Bug
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode

Comments:
Failure looks unrelated
thanks @phofl
ENH: Add BytesIOWrapper
State: closed

- [ ] closes #39383
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

Precursor for pyarrow csv reader integration.

@jorisvandenbossche Do you know if there is any workaround I can use to read StringIO's on the arrow side? Adding this wrapper feels very hacky.

Labels:
name: Enhancement
name: Refactor
description: Internal refactoring of code
name: IO Data
description: IO issues that don't fit into a more specific label

Comments:
gentle ping @jreback @jorisvandenbossche this is blocking integration of the pyarrow csv reader.
thanks @lithomas1 very nice! and thanks @twoertwein for reviewing
BUG: compute.use_numexpr option not respected
State: closed

- [x] closes #32556
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry


Labels:
name: Bug
name: Algos
description: Non-arithmetic algos: value_counts, factorize, sorting, isin, clip, shift, diff

Comments:
also look thru the referenced issue for any other things that we can test with this. it is quite trick to make sure this is working propertly.
lgtm. over to you @MarcoGorelli 
thanks @saehuihwang
Update frame.py
State: closed

Added an example to the reorder_levels function

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:
name: Docs

Comments:
Hello @trevorkask! Thanks for opening this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:

* In the file [`pandas/core/frame.py`](https://github.com/pandas-dev/pandas/blob/34a53d1b9bdbfdf5098704d10c566cad6612208b/pandas/core/frame.py):

> [Line 6791:1](https://github.com/pandas-dev/pandas/blob/34a53d1b9bdbfdf5098704d10c566cad6612208b/pandas/core/frame.py#L6791): [W293](https://duckduckgo.com/?q=pep8%20W293) blank line contains whitespace
> [Line 6794:89](https://github.com/pandas-dev/pandas/blob/34a53d1b9bdbfdf5098704d10c566cad6612208b/pandas/core/frame.py#L6794): [E501](https://duckduckgo.com/?q=pep8%20E501) line too long (96 > 88 characters)
> [Line 6821:1](https://github.com/pandas-dev/pandas/blob/34a53d1b9bdbfdf5098704d10c566cad6612208b/pandas/core/frame.py#L6821): [W293](https://duckduckgo.com/?q=pep8%20W293) blank line contains whitespace


the linter has a few complaints
closing in favor of #42935
TST: Test Loc to set Multiple Items to multiple new columns
State: closed

- [x] closes #25594
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry
added test to pandas/tests/indexing/multi/test_loc.py

Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: Indexing
description: Related to indexing on series/frames, not to indexes themselves

Comments:
Hello @GYvan! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:



There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2021-07-27 15:01:12 UTC
Thanks @GYvan for the PR. There are some lint failures and another git commit.

see https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#working-with-the-code 
> Thanks @GYvan for the PR. There are some lint failures and another git commit.
> 
> see https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#working-with-the-code

Thanks, I will look through them
> Thanks @GYvan for the PR. There are some lint failures and another git commit.
> 
> see https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#working-with-the-code


> > Thanks @GYvan for the PR. There are some lint failures and another git commit.
> > see https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#working-with-the-code



> Thanks @GYvan for the PR. There are some lint failures and another git commit.
> 
> see https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#working-with-the-code


Hi @simonjayhawkins. I have tried to address the lint failures and reverted the unrelate changes. Can you please let me know if anything else needs changes?

cc @phofl
lgtm. @phofl merge when ready
Thanks @GYvan
move release note for fix for #42259
State: closed

xref #42660, https://github.com/pandas-dev/pandas/issues/42259#issuecomment-884870958

release note is moved in backport #42660, so this PR does not need backport.

Labels:
name: Docs

Comments:
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 d98c92c07d93e21a3105175688f55232b4838f30
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #42661: move release note for fix for #42259'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-42661-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #42661 on branch 1.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
TYP: Update input of `core.algorithms.duplicated`
State: closed

- [x] closes #42604
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:
name: Typing
description: type annotations, mypy/pyright type checking
name: Stale

Comments:
This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this.
Thanks for the pull request, but although its still a draft, it has appeared to have gone stale. If you're still interested in working on this let us know and we can reopen.
TST: test transform('cumcount')
State: closed

- [x] closes #27472
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them



Labels:
name: Testing
description: pandas testing functions or related to the test suite

Comments:
Thanks @saehuihwang
DOC: fix small typo in HDF section of cookbook docs
State: closed

This merge request fixes a trivial typo (diver -> driver) I found while reading docs about HDF support.

- [-] closes #xxxx
- [-] tests added / passed
- [-] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [-] whatsnew entry


Labels:
name: Docs

Comments:
Thanks @claws
TST: Add test for setitem preserving period dtype 
State: closed

- [x] closes #26861
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them



Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Period
description: Period data type

Comments:
thanks @zeitlinv
BUG: EWM silently failed float32
State: closed

- [x] closes #42452
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry


Labels:
name: Bug
name: Dtype Conversions
description: Unexpected or buggy dtype conversions
name: Window
description: rolling, ewma, expanding

Comments:
cc @mroeschke 
Hi @jreback . Sorry I don't follow.
> we certainly don't support float16

Are you saying I should remove float16 here? 
`converted_dtypes.extend([np.float64, np.float32, np.float16])`


>this is not actually testing the result is correct

I have changed the earlier test (where I was just comparing the shape), to include constant data. I am comparing the result now(after @mroeschke suggested).




@debnathshoham does this fix also close #41779
hi @simonjayhawkins,
I am getting the below right now (i.e. columns a with float16 is getting dropped)
```
      b     c     d     e     f
0   1.0   1.0   2.0   3.0   4.0
1   7.0   7.0   8.0   9.0  10.0
2  13.0  13.0  14.0  15.0  16.0
3  19.0  19.0  20.0  21.0  22.0
```

Adding float16 as well to the `converted_dtypes` list, would fix that as well.
alternatively, i can see that just replacing with "number" below also fixes both (as suggested in the other BUG)
`obj = obj.select_dtypes(include=["integer", "float"], exclude=["timedelta"])`
we are not supporting float16 in any way
Hi @jreback, then this patch should work fine. Pls let me know if you think of any other changes I should make. 
Thanks @debnathshoham
Revert 42231 bug mi should compare
State: closed

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:

Comments:
Note that this PR is not onto master, but from my fork of the "revert-..." branch onto pandas-dev form of the same branch.  I couldn't find any other way to merge master on that branch.
Not sure what happened here, but this is a duplicate of #42575, closing.
DOC: Boolean Array Is Experimental
State: closed

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

BooleanArray and BooleanDtype are marked experimental, but its not marked as experimental in the user guide.

Labels:
name: Docs

Comments:
thanks @lithomas1 
@meeseeksdev backport 1.3.x
Something went wrong ... Please have  a look at my logs.
BUG: ArrayManager reindex with copy=True not copying
State: closed

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:
name: Bug

Comments:
thanks, can you add on a whatsnew note at some point.
BUG: misleading error creating df from 2d array
State: closed

- [x] closes #42463
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry


Labels:
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Error Reporting
description: Incorrect or improved errors from pandas

Comments:
`FAILED pandas/core/groupby/groupby.py::pandas.core.groupby.groupby.GroupBy.apply`
Failure unrelated to my change
@debnathshoham lgtm. can you add a whatsnew note (bug fixes for reshaping for 1.4 is good), a short note about the revised error that a user would see. ping on green.
@jreback Green-ish (unrelated failures)
thanks @debnathshoham
BUG: KeyError when a series popped from data frame with bool indexer
State: closed


- [x] closes #42530
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry


Labels:
name: Bug
name: Indexing
description: Related to indexing on series/frames, not to indexes themselves

Comments:
thanks @debnathshoham 
@meeseeksdev backport 1.3.x
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 28ea152c33fc88c6c0607d2ae02e96933a9b26dd
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #42644: BUG: KeyError when a series popped from data frame with bool indexer'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-42644-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #42644 on branch 1.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
@simonjayhawkins you are right, the release note is in the wrong place.
just doing the backport now with the release note in 1.3.2. and then a separate PR to move the release note (which won't need a backport, unless we get conflicts in the meantime and I need to resync)
ENH: add kw `levels` to `Styler.hide_index` to hide only specific levels
State: closed

- [x] closes #25475
- [x] tests added / passed
- [x] whatsnew entry 1.4.0

![Screen Shot 2021-07-21 at 14 13 35](https://user-images.githubusercontent.com/24256554/126486650-af383d0b-3372-4c19-bb4a-db19dff25e6f.png)


Labels:
name: Enhancement
name: Styler
description: conditional formatting using DataFrame.style

Comments:
@jreback pinging on green
failures unrelated
pd.to_datetime() fails for KeyError when raising monotonic increasing index ValueError
State: closed

- [x] closes #28238
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

Test added to test_to_datetime.py to test the conversion to datetime for a series with a float index.

Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: Datetime
description: Datetime data dtype

Comments:
thanks @usersblock
CI: Try to speed up ArrayManager
State: closed

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

Don't re-run ArrayManager tests if we are already in ArrayManager mode.

P.S. I'm not sure what the arraymanager marker is supposed to be for. If it only runs the frame tests, wouldn't it be better to just specify that directly in the ``PYTEST_AM_CMD``.


Labels:
name: CI
description: Continuous Integration

Comments:
did this improve the CI time as intended?
Its around 2 min. or ~5% of time. 
ok this is fine
Fixed regression for SettingWithCopyWarning showing incorrect stacklevel
State: closed

- [x] closes #42570
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

Is there a better way to check the stacklevel here?



Labels:
name: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Regression
description: Functionality that used to work in a prior pandas version
name: Copy / view semantics

Comments:
merging