BrandonFors/pandas-github-issues huggingface dataset:
DOC Change slack invitation from email to link
State: closed

Simplified the slack invitation process after discussion with @rhshadrach and @MarcoGorelli.

The current email process is maintenance heavy and until now, we received very little spam. We want to try letting people join themselves and see if spam increases or not.

Local build looked correct.

Labels:
name: Docs

Comments:
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/52014/
I think we can merge now, tag has been pushed
DEPS: Filter numpy's FutureWarning from array_equal
State: closed

Looks to be failing on the numpy dev build

The warning is from `np.array_equal` raising it's own FutureWarning: https://github.com/numpy/numpy/issues/23401

Labels:
name: Warnings
description: Warnings that appear or should be added to pandas
name: Upstream issue
description: Issue related to pandas dependency

Comments:
LGTM pending green
Looks like the numpy dev build is installing a non-numpy dev version for some reason: https://github.com/pandas-dev/pandas/actions/runs/4432829243/jobs/7777266394

`Requirement already satisfied: numpy>=1.21.0 in /home/runner/micromamba/envs/test/lib/python3.10/site-packages (from pandas==2.1.0.dev0+239.g69b7019c10) (1.24.2)`
Looked to have been an environment solve/cache issue, but I suppose this could be useful to still filter this out.
The 2.0.x build is still failing as of this morning, so merging and backporting
thx @mroeschke 
Purging the cache there helped as well
CoW: Avoid copying Index in Series constructor
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Index
description: Related to the Index class or subclasses
name: Series
description: Series data structure
name: Copy / view semantics

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 2.0.x
git pull
```

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

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

```
git commit -am 'Backport PR #52008: CoW: Avoid copying Index in Series constructor'
```

4. Push to a named branch:

```
git push YOURFORK 2.0.x:auto-backport-of-pr-52008-on-2.0.x
```

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

> "Backport PR #52008 on branch 2.0.x (CoW: Avoid copying Index in Series constructor)"

And apply the correct labels and milestones.

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

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
TYP/CLN: remove no-longer-needed overrides
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


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

Comments:
Thanks @jbrockmendel
DEPR: NDFrame._data
State: closed

- [x] closes #33333 (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Deprecate
description: Functionality to remove in pandas

Comments:
thx @jbrockmendel
DEPR: DFGB.dtypes, rolling axis, Categorical.to_list
State: closed

- [ ] 
closes #51254
Reverted that part
- [x] closes #51045
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Deprecate
description: Functionality to remove in pandas

Comments:
`Categorical.to_list` is the only one that we may want to deprecate the other way instead? xref https://github.com/pandas-dev/pandas/issues/14278 https://github.com/pandas-dev/pandas/issues/8826
w/r/t to_list/tolist i dont have an opinion, just dont want an outlier.  (also i dont expect people to use Categorical directly that much)
Yeah likewise. I would just recommend tabling `Categorical.to_list` until there's some more steam around which to list variant we want everywhere.
sure, will update
updated + green, will handle Categorical.to_list in an upcoming DEPR PR
Thanks @jbrockmendel
CI: Unpin matplotlib
State: closed

- [ ] closes #51394 (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

lets see if the new release addresses the failures

Labels:
name: Visualization
description: plotting
name: CI
description: Continuous Integration

Comments:
cc @mroeschke I think you took a closer look at the failures when 3.7 came out. Is this test failure expected and we have to fix it or is it on the matplotlib side?
I don't remember seeing `UserWarning: All values for SymLogScale are below linthresh, making it effectively linear. You likely should lower the value of linthresh.` in the previous release. I suppose we can catch this in our test.

For `AttributeError: 'NoneType' object has no attribute 'rowspan'` I think we have to address this on our side. I tried addressing it with this (undo) commit but it caused other test failures I didn't really understand :/
https://github.com/pandas-dev/pandas/pull/51470/commits/a36f00790a5468186869b8e0dc186cc6189bb672
#52150 fixes one of the errors.

The other failure I think you should fix by making the data range bigger with your test data or add a warning filter to that test.
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 2.0.x
git pull
```

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

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

```
git commit -am 'Backport PR #51990: CI: Unpin matplotlib'
```

4. Push to a named branch:

```
git push YOURFORK 2.0.x:auto-backport-of-pr-51990-on-2.0.x
```

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

> "Backport PR #51990 on branch 2.0.x (CI: Unpin matplotlib)"

And apply the correct labels and milestones.

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

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
DOC: Remove whatsnew after backport
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Docs
name: Arrow
description: pyarrow functionality

Comments:
Thanks @phofl
Backport PR #51643 on branch 2.0.x (API: ArrowExtensionArray._cmp_method to return pyarrow.bool_ type)
State: closed

#51643

- [x] closes #51980

Labels:
name: Arrow
description: pyarrow functionality

Comments:
@lukemanley could you take a look at the doctest failures? Is this expected to fail?
> @lukemanley could you take a look at the doctest failures? Is this expected to fail?

looks like you already identified #51631 needs to be back-ported first
Yep, thx
BUG: Add numpy_nullable support to arrow csv parser
State: closed

- [x] closes #51852 (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: IO CSV
description: read_csv, to_csv
name: Arrow
description: pyarrow functionality

Comments:
Thanks @phofl
integer array creation test GH#31104
State: closed


- [ ] closes #31104 (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).


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

Comments:
Thanks again @liang3zy22
BUG: map method on datetimelikes should not work arraywise
State: closed

- [x] closes #51977
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Bug
name: Datetime
description: Datetime data dtype

Comments:
Thanks @topper-123 
> _Could_ be framed as an API change, but I am okay with calling this a bug especially since dicts/Series map elements.

Thanks. I was on the fencer too, but think I would feel it was  a bug if this didn't work elementwise + the code is so much cleaner now:-)
BUG/API: preserve non-nano in factorize/unique
State: closed

- [ ] closes #51961 (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

The ugly bit here is that it causes `to_datetime` to behave slightly differently with cache=True/False in some cases.  I know @mroeschke worked to avoid that in #17077, so it may be a deal-breaker.

But it fixes #51961 (though doesn't yet have a targeted test) so may be worth prioritizing (cc @MarcoGorelli)

(Update) also fixes Series[non-nano].factorize which currently raises AssertionError

Labels:
name: Algos
description: Non-arithmetic algos: value_counts, factorize, sorting, isin, clip, shift, diff
name: Non-Nano
description: datetime64/timedelta64 with non-nanosecond resolution

Comments:
> But it fixes https://github.com/pandas-dev/pandas/issues/51961 (though doesn't yet have a targeted test) so may be worth prioritizing

Fine with me to have this fix despite the cache=False bug. Could you add a test for the above too?
Thanks @jbrockmendel 
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 2.0.x
git pull
```

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

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

```
git commit -am 'Backport PR #51978: BUG/API: preserve non-nano in factorize/unique'
```

4. Push to a named branch:

```
git push YOURFORK 2.0.x:auto-backport-of-pr-51978-on-2.0.x
```

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

> "Backport PR #51978 on branch 2.0.x (BUG/API: preserve non-nano in factorize/unique)"

And apply the correct labels and milestones.

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

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
Mind creating the backport PR @jbrockmendel ?
BUG: read_csv for arrow with mismatching dtypes does not work
State: closed

- [x] closes #51876 (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: IO CSV
description: read_csv, to_csv

Comments:
Thanks @phofl 
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 2.0.x
git pull
```

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

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

```
git commit -am 'Backport PR #51976: BUG: read_csv for arrow with mismatching dtypes does not work'
```

4. Push to a named branch:

```
git push YOURFORK 2.0.x:auto-backport-of-pr-51976-on-2.0.x
```

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

> "Backport PR #51976 on branch 2.0.x (BUG: read_csv for arrow with mismatching dtypes does not work)"

And apply the correct labels and milestones.

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

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
Grouper documentation update
State: closed


Labels:
name: Docs
name: Groupby
name: Stale

Comments:
Could you add an example in the `Example` section of this behavior? Also the CI checks look to be failing
This pull request is stale because it has been open for thirty days with no activity. Please [update](https://pandas.pydata.org/pandas-docs/stable/development/contributing.html#updating-your-pull-request) and respond to this comment if you're still interested in working on this.
Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.
BUG: astype_view check raising on minimum versions build
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

This code path was never hit on the min versions build. Stumbled upon this on another pr

Labels:
name: Dtype Conversions
description: Unexpected or buggy dtype conversions

Comments:
I'll merge this to get into the rc
CLN: Assorted
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:

Comments:
Thanks @jbrockmendel
REF/TYP: avoid need for NDFrameTb
State: closed

We have a method align_as_utc that implemented at the module-level instead of as a method, requiring some annotation gymnastics.  This refactors so that it is only used in one place instead of two, then inlines the function inside `align`.

Labels:
name: Refactor
description: Internal refactoring of code
name: Typing
description: type annotations, mypy/pyright type checking

Comments:
Thanks @jbrockmendel
DEPR: method, limit, fill_axis keywords in align
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

xref #51856, closes if we decide we don't want to deprecate broadcast_axis

Labels:
name: Deprecate
description: Functionality to remove in pandas

Comments:
thx @jbrockmendel
Series.plot doesn't allow color=None
State: closed

- [X] closes #51953
- [X] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [X] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [X] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Visualization
description: plotting

Comments:
> Can you add a whatsnew? Otherwise lgtm

sure, done.
thx @dannyi96 
Thanks!
CoW: __array__ not recognizing ea dtypes
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Copy / view semantics

Comments:
@jorisvandenbossche this would be nice to get into 2.0
Merging to get into 2.0
DEPR: DataFrame.swapaxes
State: closed

- [x] closes #51946  (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Deprecate
description: Functionality to remove in pandas

Comments:
Thanks @luke396
Add replace test for nil gh32075
State: closed

- [ ] closes #32075
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).


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

Comments:
Thanks @liang3zy22