BrandonFors/pandas-github-issues huggingface dataset:
DEPS: Drop Python 3.9
State: closed

Dropping Python 3.9 support per [NEP 29](https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table) and [SPEC-0](https://scientific-python.org/specs/spec-0000/#support-window)

Labels:
name: Build
description: Library building on various platforms
name: Dependencies
description: Required and optional dependencies

Comments:
I think there are a few `sys.version_info` left that compare aginst 3.10, for example, in [pandas._typing](https://github.com/pandas-dev/pandas/blob/b9bfc0134455d8a5f269366f87d2a8567aa4269c/pandas/_typing.py#L95C8-L95C24). Pyupgrades's `--py310-plus` might take care of that automatically (currently set to 3.9)
> Do we want to wait until we get closer to 3.0 release to merge?

I guess we could merge anytime, but I would wait a little just in case people are still using 3.9 nightlies
Are people OK with doing this now?

We're coming up on the Python 3.10 drop date (end of this year) as well.

I would personally prefer dropping as close to the date specified by SPEC 0, so people aren't surprised when this happens.
Since it seemed like there was approval a few months ago, I'll merge at the end of the week if there are no objections
Works for me
DOC: Enforce Numpy Docstring Validation for pandas.ExcelFile, pandas.ExcelFile.parse and pandas.ExcelWriter
State: closed

- [ ] xref #58067
- [ ] [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: IO Excel
description: read_excel, to_excel

Comments:
This PR is ready for review. Thanks.
Thanks @tuhinsharma121
CLN: enforce the deprecation of the `Series.argsort` NA behavior
State: closed

xref #54219
enforced the deprecation of the `Series.argsort` `NA` behavior.

closes https://github.com/pandas-dev/pandas/issues/12694
closes https://github.com/pandas-dev/pandas/issues/43840

Labels:
name: Clean

Comments:
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 @natmokval 
thanks @mroeschke for reviewing this PR
ENH: Allow parameter  min_periods in DataFrame.corrwith()
State: closed

- [x] closes #9490
- [ ] [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: Reduction Operations
description: sum, mean, min, max, etc.

Comments:
Thanks @weikhor
ASV: benchmark for DataFrame.Update
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.

@rhshadrach and @datapythonista 

Benchmarks for the DataFrame.Update method are implemented, as suggested on PR #57637 by @datapythonista and based on the manual tests done by @rhshadrach on #55634. By running ASV locally we measure the change in the performance due to the fix on #57637, as indicated below:

| Change   | Main (2.2.1) [8da8b544]   | PR (3.0) [93ea131f]  |   Ratio | Benchmark (Parameter)                                   |
|----------|----------------------------|----------------------------------------|---------|---------------------------------------------------------|
| -        | 1.13±0.02ms                | 887±10μs                               |    0.78 | frame_methods.Update.time_to_update_random_indices      |
| -        | 1.19±0.02ms                | 840±9μs                                |    0.71 | frame_methods.Update.time_to_update_small_frame_big_arg |
| -        | 1.27±0.01ms                | 859±9μs                                |    0.67 | frame_methods.Update.time_to_update_big_frame_small_arg |

Regards




Labels:
name: Benchmark
description: Performance (ASV) benchmarks

Comments:
> Can you increase the parameters to get runtime up to ~10ms.

@rhshadrach Think I am done here.

Data was increased twofold, from $10^4$ to $10^6$ points. Each test is now taking ~4ms. Didn't check the scaling, but it seems to be enough because the data size is similar to other benchmarks in the `frame_methods.py`. If needed, I can increase the data again. 

| Change   | Before [4fe49b16] <main>   | After [93ea131f] <fix_gh55509_v2~14>   |   Ratio | Benchmark (Parameter)                                   |
|----------|----------------------------|----------------------------------------|---------|---------------------------------------------------------|
| -        | 4.47±0.01ms                | 3.79±0.1ms                             |    0.85 | frame_methods.Update.time_to_update_big_frame_small_arg |
| -        | 4.31±0.03ms                | 3.06±0.03ms                            |    0.71 | frame_methods.Update.time_to_update_random_indices      |
| -        | 2.94±0.02ms                | 1.10±0.01ms                            |    0.37 | frame_methods.Update.time_to_update_small_frame_big_arg |



It would be interesting to have some guidance on the best data size for a useful test, but that would be a whole work on itself.

EDIT: Table
Thanks @aureliobarbosa!
BUG: Timestamp ignoring explicit tz=None
State: closed

- [x] closes #48688(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.
- [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: Timezones
description: Timezone data dtype
name: Timestamp
description: pd.Timestamp and associated methods

Comments:
Thanks @tqa236
DOC: Fix docstring error for pandas.DataFrame.axes
State: closed

- Fixes docstring error for pandas.DataFrame.axes method (https://github.com/pandas-dev/pandas/issues/58065).
- [ ] [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.

Closed previous PR https://github.com/pandas-dev/pandas/pull/58102 and re-opened here.

Labels:
name: Docs

Comments:
Thanks @v-lozko
Revert "CI: Pin blosc to fix pytables"
State: closed

Reverts pandas-dev/pandas#58209

Labels:
name: CI
description: Continuous Integration

Comments:
Thanks @lithomas1 
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.2.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 8b6a82f35a9dd8437564b50631b86b6a7e8c0251
```

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

```
git commit -am 'Backport PR #58218: Revert "CI: Pin blosc to fix pytables"'
```

4. Push to a named branch:

```
git push YOURFORK 2.2.x:auto-backport-of-pr-58218-on-2.2.x
```

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

> "Backport PR #58218 on branch 2.2.x (Revert "CI: Pin blosc to fix pytables")"

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).
                
@lithomas1 was https://github.com/pandas-dev/pandas/pull/58209 ever backported? We can remove the needs backport label here?

and change the milestones?
This wasn't needed for 2.2.3. 

Thanks for checking.
I think this is causing problems for 2.2.x now, backporting.
DOC: update DatetimeTZDtype unit limitation
State: closed

- [x] closes #58212
- [ ] [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

Comments:
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/58213/
Thanks @yokomotod
CI: Pin blosc to fix pytables
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: CI
description: Continuous Integration

Comments:
self merging to make CI green.
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.2.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 b1525c4a3788d161653b04a71a84e44847bedc1b
```

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

```
git commit -am 'Backport PR #58209: CI: Pin blosc to fix pytables'
```

4. Push to a named branch:

```
git push YOURFORK 2.2.x:auto-backport-of-pr-58209-on-2.2.x
```

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

> "Backport PR #58209 on branch 2.2.x (CI: Pin blosc to fix pytables)"

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).
                
Upstream fixed this now, this should be reverted to not cause issues in future
DOC: Add release date/contributors for 2.2.2
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

Comments:
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/58203/
DOC/TST: Document numpy 2.0 support and add tests for string array
State: closed

- [ ] closes #58104  (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: Testing
description: pandas testing functions or related to the test suite
name: Docs
name: Compat
description: pandas objects compatability with Numpy or Python functions

Comments:
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/58202/
I don't know where to ask: Is there a ETA for pandas 2.2.2 with numpy 2.0(rc) support?
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.2.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 5232bee8df3b57766c44b62152aa3fdd24e40ada
```

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

```
git commit -am 'Backport PR #58202: DOC/TST: Document numpy 2.0 support and add tests for string array'
```

4. Push to a named branch:

```
git push YOURFORK 2.2.x:auto-backport-of-pr-58202-on-2.2.x
```

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

> "Backport PR #58202 on branch 2.2.x (DOC/TST: Document numpy 2.0 support and add tests for string array)"

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).
                
> I don't know where to ask: Is there a ETA for pandas 2.2.2 with numpy 2.0(rc) support?

Release is expected to happen today.
@lithomas1 Thanks for the prompt and quite pleasing response 😃
Fix ASV with virtualenv
State: closed

The default remains conda, but this is needed if you ever change the default locally. Otherwise you get

   STDERR -------->
   /home/willayd/clones/pandas/asv_bench/env/7e437c4d615a12609229592196e74215/bin/python: No module named build

Labels:
name: Benchmark
description: Performance (ASV) benchmarks

Comments:
Thanks @WillAyd
Remove unused tslib function
State: closed

Flagged during compilation

[22/27] Compiling C object pandas/_libs/tslib.cpython-310-x86_64-linux-gnu.so.p/meson-generated_pandas__libs_tslib.pyx.c.o
  pandas/_libs/tslib.cpython-310-x86_64-linux-gnu.so.p/pandas/_libs/tslib.pyx.c:27000:18: warning: '__pyx_f_6pandas_5_libs_5tslib__array_with_unit_to_datetime_object_fallback' defined but not used [-Wunused-function]


Labels:
name: Internals
description: Related to non-user accessible pandas implementation
name: Clean

Comments:
nice!
Thanks @WillAyd
Add low-level create_dataframe_from_blocks helper function
State: closed

See my explanation at https://github.com/pandas-dev/pandas/issues/56815/

- [ ] 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).
- [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: API Design
name: Internals
description: Related to non-user accessible pandas implementation

Comments:
Not my favorite thing in the world, but better than the status quo so i'm on board.
I added some basic roundtrip tests and tests for the corner cases that I am aware of (the numpy arrays instead of EA for datetime/timedelta, and passing 1D EAs for cases that are stored 2D internally). 
(and using this in pyarrow is also passing the test suite there)
@jbrockmendel @phofl could I get a more in-depth review (if there are remaining comments)? I would like to get the change to use this included in pyarrow 16, so we don't have to worry about deprecation warnings when merging https://github.com/pandas-dev/pandas/pull/57754 for 3.0 (for the case of using the latest released version of both libraries), but then I need to get this in in the coming days.

Small reminder here
thx @jorisvandenbossche
TST: Add tests for reading Stata dta files saved in big-endian format
State: closed

- [x] closes #58194
- [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.
- [ ] 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: Testing
description: pandas testing functions or related to the test suite
name: IO Stata
description: read_stata, to_stata

Comments:
Thanks @cmjcharlton
CLN: enforce deprecation `resample` with `PeriodIndex`
State: closed

enforced deprecation of `resample` with `PeriodIndex`



Labels:

Comments:
I have a Pr that does this, but it is on hold bc a handful of people are asking us to reconsider the deprecation
> I have a Pr that does this, but it is on hold bc a handful of people are asking us to reconsider the deprecation

thanks, I understand. I'll close this PR.
BUG: Let check_exact_index default to True for integers
State: closed

- [ ] closes #57386
- [ ] [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: Testing
description: pandas testing functions or related to the test suite

Comments:
No problem at all. Not sure how many tests are needed but I think this should be sufficient
Thanks @Aloqeely
TST: catch exception for div/truediv operations between Timedelta and pd.NA
State: closed

- [x] closes #54315
- [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).
- [Not applicable] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [Not applicable] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

This PR add a test to catch ``TypeError`` raised by div and true div operations between ``Timedelta`` and ``pd.NA``.

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

Comments:
Thanks @droussea2001 
You're welcome !
CI: correct error msg in `test_view_index`
State: closed

CI failed, the reason: `AssertionError: Regex pattern did not match.`

Replaced error msg `'Cannot change data-type for object array'` with `'Cannot change data-type for array of references.'`

Labels:
name: CI
description: Continuous Integration

Comments:
Thanks for the quick fix!
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.2.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 f56cba900e9f035b54519a0aa7d027bef01fc50b
```

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

```
git commit -am 'Backport PR #58181: CI: correct error msg in `test_view_index`'
```

4. Push to a named branch:

```
git push YOURFORK 2.2.x:auto-backport-of-pr-58181-on-2.2.x
```

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

> "Backport PR #58181 on branch 2.2.x (CI: correct error msg in `test_view_index`)"

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).
                
@natmokval mind doing the backport?
> @natmokval mind doing the backport?

sure, I'll do the backport