BrandonFors/pandas-github-issues huggingface dataset:
BUG: DataFrame construction with dictionary ArrowDtype columns
State: closed

- [ ] closes #53617 (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: Constructors
description: Series/DataFrame/Index/pd.array Constructors
name: Arrow
description: pyarrow functionality

Comments:
Looks to be greenish so merging, but can follow up if needed
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 d36da2b77c4e9b6a7e5064bde0f2775bcf989c69
```

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

```
git commit -am 'Backport PR #53654: BUG: DataFrame construction with dictionary ArrowDtype columns'
```

4. Push to a named branch:

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

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

> "Backport PR #53654 on branch 2.0.x (BUG: DataFrame construction with dictionary ArrowDtype columns)"

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).
BUG: Indexing a timestamp ArrowDtype Index
State: closed

- [x] closes #53644 (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: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Arrow
description: pyarrow functionality

Comments:
small comment, also needs rebase.  otherwise LGTM
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 f0d3301a4193bb8f567edd7d1e10ad8ae3a16193
```

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

```
git commit -am 'Backport PR #53652: BUG: Indexing a timestamp ArrowDtype Index'
```

4. Push to a named branch:

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

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

> "Backport PR #53652 on branch 2.0.x (BUG: Indexing a timestamp ArrowDtype 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).
BUG: convert_dtype(dtype_backend=nullable_numpy) with ArrowDtype
State: closed

- [x] closes #53648 (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: Dtype Conversions
description: Unexpected or buggy dtype conversions
name: Arrow
description: pyarrow functionality

Comments:
Going to merge, but happy to address followups in a separate PR
DOC: Fixing EX01 - Added examples
State: closed

- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

Towards https://github.com/pandas-dev/pandas/issues/37875


Labels:
name: Docs

Comments:
@MarcoGorelli - It looks green
Thanks @DeaMariaLeon
ENH: Series.str.join for ArrowDtype(pa.string())
State: closed

- [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/v2.1.0.rst` file if fixing a bug or adding a new feature.

Adds support for `Series.str.join` with `ArrowDtype(pa.string())`:

```
In [1]: from pandas import Series, ArrowDtype

In [2]: import pyarrow as pa

In [3]: ser = Series(["abc", "123", None], dtype=ArrowDtype(pa.string()))

In [4]: ser.str.join("-")
Out[4]: 
0    a-b-c
1    1-2-3
2     <NA>
dtype: string[pyarrow]
```


This is already supported by `string[python]` and `string[pyarrow]` as well as python strings in general:

```
In [1]: "-".join("abc")
Out[1]: 'a-b-c'
```

This is work towards being able to add `ArrowDtype(pa.string())` to the string benchmarks.

Labels:
name: Strings
description: String extension data type and string data
name: Arrow
description: pyarrow functionality

Comments:
Nice find thanks @lukemanley
DEPR: interpolate with object dtype
State: closed

- [x] closes #53631 (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.

I'd also be OK with just deprecating object-with-nans

Labels:
name: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate
name: API Design
name: Deprecate
description: Functionality to remove in pandas

Comments:
Yeah makes sense to deprecate. Thanks @jbrockmendel
BUG: DataFrame.stack with sort=True and unsorted MultiIndex levels
State: closed

- [x] closes #53636 (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: Bug
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode

Comments:
Nice! Thanks @rhshadrach
BUG: interpolate with complex dtype
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.


Labels:
name: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate

Comments:
Thanks @jbrockmendel
BUG: fix datetimeindex repr
State: closed

- [x] closes #53470 
- [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.

Slightly modified `_is_dates_only` in `DatetimeIndex` as mentioned in the issue.


Labels:
name: Datetime
description: Datetime data dtype
name: Output-Formatting
description: __repr__ of pandas objects, to_string

Comments:
I added some remarks about this PR in: https://github.com/pandas-dev/pandas/issues/53470

Unfortunately, I do not know much about DatetimeArrays to be to help.
@topper-123 could you take a look whenever you get the chance?
@Simar-B, I added some sanity checks of my own in https://github.com/Simar-B/pandas/pull/1

Thanks @Simar-B
DOC: pd.Period and pd.period_range should document that they accept datetime, date and pd.Timestamp
State: closed

NOTE: This is a follow up to PR #53611 as I realised the issue was incompletely addressed there

- [x] closes #53038 (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
- [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: Docs
name: Period
description: Period data type

Comments:
@mroeschke I opened this PR to follow up on #53611 in addressing #53038. I realised I didn't push one last commit to the previous PR and the additional accepted types were missing from the `end` parameter of `period_range`, I only added them to `start`. I had also added a note to `freq` on `Period` indicating it is required if `value` is `None`. 

I didn't open a new issue since this still addresses the previous one, but let me know if this is not the right course of action. Thanks and sorry!
DOC: Added links to GitHub tutorials/resources for Forking Workflow in contributing.rst
State: closed

- [x] closes #53626 (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
- [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.

In the **contributing.rst file**, I have added information/navigation links to the GitHub documentation and tutorials for:
 1) contributing to projects
 2) forking a repo 
 3) collaborating with pull requests 
 4) working with forks

I added the updates to the _'Version control, Git and GitHub'_ section as the updates address GitHub workflows. 

I wanted to provide this information to aid new pandas contributors unsure of GitHub's forking process. I found these resources to be very helpful references when reviewing the contributing guide. Attaching a screenshot below of my local build with the changes (bordered in red). 
<img width="511" alt="contributing rst GitHub tutorial links" src="https://github.com/pandas-dev/pandas/assets/87046544/ce8c04c4-4f98-4a77-a251-58fd10469b71">

Labels:
name: Docs

Comments:
Thanks @ssharp0
TYP: core.missing
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: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate
name: Typing
description: type annotations, mypy/pyright type checking

Comments:
Thanks @jbrockmendel
ENH: add numeric_only to Dataframe.cum* methods
State: closed

- [X] closes #53072 
- [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:

Comments:
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: groupby sum turning `inf+inf` and `(-inf)+(-inf)` into `nan`
State: closed

- [x] Closes #53606
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests)
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit)
- [x] Added an entry in the latest `doc/source/whatsnew/v2.1.0.rst` file

This modifies `group_sum` in almost the way as #52964 for `group_mean`.

Labels:
name: Bug
name: Groupby
name: Reduction Operations
description: sum, mean, min, max, etc.

Comments:
@Charlie-XIAO - small note, we like to use `BUG:` instead of `FIX`. See

https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#finally-make-the-pull-request

for more details.
> @Charlie-XIAO - small note, we like to use `BUG:` instead of `FIX`. See
> 
> 
> 
> https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#finally-make-the-pull-request
> 
> 
> 
> for more details.

Oh sure, sorry about that. I mixed up with the prefix of another project lol.
Thanks @Charlie-XIAO!
BUG: clean_fill_method failing to raise
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: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate

Comments:
updated+green
Thanks @jbrockmendel
DOC: pd.Period and pd.period_range should document that they accept datetime, date and pd.Timestamp
State: closed

- [x] closes #53038 (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
- [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: Docs
name: Period
description: Period data type

Comments:
Thanks @ABizzinotto
Add new `df.select()` method, plus tests and docs
State: closed

- [x] No issues to close
- [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/v2.1.0.rst` file if fixing a bug or adding a new feature.

The existing [`DataFrame.loc`][docs-pandas-DataFrame.loc] method works just fine. However, the naming convention is inconsistent with other languages and packages.

- SQL source has the name [`SELECT`][docs-sql-SELECT]
- PySpark has the method [`DataFrame.select`][docs-pyspark-DataFrame.select]
- PyPolars has the method [`DataFrame.select`][docs-polars-DataFrame.select]

By adding this `pandas.DataFrame.select()` method, we will be bringing the naming convention in line with other languages and packages.

Under-the-hood, this new method is not implementing any new logic or functionality. It's only a pass-through method to the `DataFrame.loc` method.

The equivalent of running: `df.select('column')`
Is the same as running: `df.loc[:, ['column'])`

All docs and tests have been added and are passing.

[docs-pandas-DataFrame.loc]: https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.loc.html
[docs-sql-SELECT]: https://en.wikipedia.org/wiki/Select_(SQL)
[docs-pyspark-DataFrame.select]: https://spark.apache.org/docs/3.1.1/api/python/reference/api/pyspark.sql.DataFrame.select.html
[docs-polars-DataFrame.select]: https://pola-rs.github.io/polars/py-polars/html/reference/dataframe/api/polars.DataFrame.select.html

Labels:

Comments:
Thanks for the request but as mentioned the project has rejected this method name before and generally want to avoid expanding the APi for methods that are wrappers around existing methods, closing
DEPR: NDFrame.interpolate with ffill/bfill methods
State: closed

- [x] closes #53581 (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: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate

Comments:
Thanks @jbrockmendel
DOC: Fixed inconsistencies in pandas.DataFrame.pivot_table docstring parameter descriptions
State: closed

- [x] closes #53351
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

Updated the docstring for `pandas.DataFrame.pivot_table` as described in issue #53351

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

Comments:
I see that the "Test (not single_cpu)" is failing but I am unsure how the changes I made to the `pivot_table` docstring could have resulted in the test failure. If you could provide any direction about anything I could do on my end to rectify this, I will update it accordingly. Thanks!
Thanks @tpaxman
ENH: Series.explode to support pyarrow-backed list types
State: closed

- [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/v2.1.0.rst` file if fixing a bug or adding a new feature.


Labels:
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Arrow
description: pyarrow functionality

Comments:
Thanks @lukemanley
Command for installation in notebook
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 for the PR, but it's not clear this is specifically pandas related so not sure it belong in the README so closing