BrandonFors/pandas-github-issues huggingface dataset:
BUG(string dtype): Resolve pytables xfail when reading with condition
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.

Continuation of #60663; the whatsnew added there covers this too.


Labels:
name: IO HDF5
description: read_hdf, HDFStore
name: Strings
description: String extension data type and string data

Comments:
Thanks @rhshadrach 
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.3.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 0ec5f2668e9568d90595180d5ee925305ec7182e
```

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

```
git commit -am 'Backport PR #60943: BUG(string dtype): Resolve pytables xfail when reading with condition'
```

4. Push to a named branch:

```
git push YOURFORK 2.3.x:auto-backport-of-pr-60943-on-2.3.x
```

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

> "Backport PR #60943 on branch 2.3.x (BUG(string dtype): Resolve pytables xfail when reading with condition)"

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).
                
Backport PR: #60967
BUG: Fixed assign failure when with Copy-on-Write
State: closed

- [x] closes #60309 
- [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.3.0.rst` file if fixing a bug or adding a new feature.


Labels:
name: Stale

Comments:
Since there has been no feedback for two weeks, just a friendly ping @mroeschke  @rhshadrach @WillAyd , thanks 🙏
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.
DOC: Add security note for Excel export with formula cells
State: closed

- [ ] closes #29095
- [ ] [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 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.
ENH(string dtype): Implement cumsum for Python-backed strings
State: closed

Follow-up on https://github.com/pandas-dev/pandas/pull/60633

Labels:
name: Strings
description: String extension data type and string data

Comments:
Thanks @rhshadrach 
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.3.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 4e20195086e5cdd5bde56da7d95cf672b795b32e
```

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

```
git commit -am 'Backport PR #60938: ENH(string dtype): Implement cumsum for Python-backed strings'
```

4. Push to a named branch:

```
git push YOURFORK 2.3.x:auto-backport-of-pr-60938-on-2.3.x
```

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

> "Backport PR #60938 on branch 2.3.x (ENH(string dtype): Implement cumsum for Python-backed strings)"

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).
                
Backport PR: #60984
BUG(string dtype): Empty sum produces incorrect result
State: closed

- [x] closes #60229 (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: Groupby
name: Missing-data
description: np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate
name: Strings
description: String extension data type and string data

Comments:
Friendly ping @WillAyd @jorisvandenbossche 
Great thanks @rhshadrach 
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.3.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 dab1b881da2d7d49200808f45942868f1953effa
```

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

```
git commit -am 'Backport PR #60936: BUG(string dtype): Empty sum produces incorrect result'
```

4. Push to a named branch:

```
git push YOURFORK 2.3.x:auto-backport-of-pr-60936-on-2.3.x
```

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

> "Backport PR #60936 on branch 2.3.x (BUG(string dtype): Empty sum produces incorrect result)"

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).
                
Backport PR -> https://github.com/pandas-dev/pandas/pull/61625
fix for #60695 fix Series constructor dropping key levels when keys have varying entry counts
State: closed

Ensures that the Series constructor preserves all key (index) levels, even when keys have different numbers of entries.
Addresses issue #60695 by maintaining consistency in index handling.


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.
DOC: Correct typos in developer guide for consistency
State: closed

Correct typos in developer guide for consistency

- [ ] 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:
Thanks @star1327p
DOC: Update two more links in pandas Ecosystem
State: closed

Update two more links in pandas Ecosystem.

1. In the table schema specification of IO, the dataprotocols.org domain has moved to datapackage.org:
https://datapackage.org/standard/table-schema/ 

2. Removed the ">" at the end of a Lux link to make it work:
https://lux-api.readthedocs.io/en/latest/source/guide/vis.html

- [ ] 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:
Thanks @star1327p
DOC: add series.info to api reference
State: closed

This was added in https://github.com/pandas-dev/pandas/pull/37320#pullrequestreview-819720418 but probably forgotten from the api reference?

- [ ] 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:
Thanks @MarcoGorelli
docs: clarify `None` case behavior for `sheet_name` in `pandas.read_excel`
State: closed

- [x] closes #60909  (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:
Thanks @ShashwatAgrawal20
DOC: Update the Numba jit links in window.rst
State: closed

Update the Numba jit links in window.rst.

Correct links:
- https://numba.readthedocs.io/en/stable/user/overview.html
- https://numba.readthedocs.io/en/stable/user/jit.html

Related to PR #60877. I did a search on ``https://numba`` in the repo, and I have corrected most links on Numba documentation. 

- [ ] 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:
Thanks @star1327p
Backport PR #60795: TST(string dtype): Resolve xfails in 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: Testing
description: pandas testing functions or related to the test suite
name: IO HDF5
description: read_hdf, HDFStore
name: Strings
description: String extension data type and string data

Comments:
This one might be a real failure https://github.com/pandas-dev/pandas/actions/runs/13273735595/job/37058952425?pr=60916
Thanks! This test was removed in #57091, removing `dtype=object` should resolve.
The remaining failures for `pandas/tests/apply/test_frame_apply.py::test_apply_raw_float_frame_lambda` are numba-related
Uniformize date format in index.html
State: closed

- [X] closes #60911 (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: Web
description: pandas website

Comments:
Sure, thanks @rffontenelle
ENH: Improved error message and raise new error for small-string NaN …
State: closed

…edge case in HDFStore.append (#60829)

* Add clearer error messages for datatype mismatch in HDFStore.append. Raise ValueError when nan_rep too large for pytable column. Add and modify applicable test code.

* Fix missed tests and correct mistake in error message.

* Remove excess comments. Reverse error type change to avoid api changes. Move nan_rep tests into separate function.

(cherry picked from commit 57340ecd08580f26ee4a976c1f68b2f563c41569)

- [ ] 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: Error Reporting
description: Incorrect or improved errors from pandas
name: IO HDF5
description: read_hdf, HDFStore

Comments:
Thanks @rhshadrach
BUG: Fix bug in DataFrame binary op not respecting fill_value in case…
State: closed

… of MultiIndex columns

- [ ] closes #60903
- [ ] [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.

When `fill_value` is not None, we should not reindex the dataframes, as the `_arith_method_with_reindex` method doesn't handle `fill_value`. Instead, we should go via the regular `_flex_arith_method` route as reindexing is no longer necessary when `fill_value` is provided.

Bug introduced in #60538 so not adding to whatsnew.

Labels:
name: Numeric Operations
description: Arithmetic, Comparison, and Logical operations
name: MultiIndex

Comments:
Thanks for the quick follow up @snitish
Bug cov nat
State: closed

- closes #53115 


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

Comments:
@jbrockmendel, @WillAyd, could you please take a look?
@jbrockmendel, I made the updates
Thanks @fbourgey 
@fbourgey could you make a follow up PR adding release notes to the 3.0 whatsnew? I think this is being called a bug fix, and not an API breaking change?
@TomAugspurger

#61586
fix: incorrect ISO week 53 conversion when only 52 weeks exist
State: closed

- [x] closes #60885 (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).
- [ ] 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: Datetime
description: Datetime data dtype

Comments:
Not sure if I'm supposed to be adding the tests in `pandas/tests/tslibs/test_strptime.py` or not. 
> Not sure if I'm supposed to be adding the tests in `pandas/tests/tslibs/test_strptime.py` or not.

You can add a test in `test_to_datetime.py` with the example from the original issue
Thanks @ShashwatAgrawal20
BUG: Prevent pd.Series.groupby from showing FutureWarning
State: closed

- [X] closes #60831
- [ ] [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.

## Linked Issue
- Future warning observed when series.groupby is called where its name is an integer. The warning seems to stem from `is_in_obj()` defined in `get_grouper()` ; Below indexing results in the warning since `gpr.name` is integer type. For example :

```python
>>>import pandas as pd
>>>arr = [['a', 'a', 'b', 'b'], ['aa', 'bb', 'aa', 'bb']]
>>>idx = pd.MultiIndex.from_arrays(arr, names=['index1', 'index2'])
>>>ser = pd.Series([10, 20, 30, 40], index=idx, name=2)
>>>ser

index1  index2
a       aa        10
        bb        20
b       aa        30
        bb        40
Name: 2, dtype: int64

>>>ser.groupby(ser)
FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`

```

## Proposed Code Change
- Since `pd.Series` doesn't have columns, added type check so that `is_in_obj()` is called only when `obj` is a `DataFrame`.

```python
    for gpr, level in zip(keys, levels):
        if isinstance(obj, DataFrame) and is_in_obj(gpr):  # df.groupby(df['name'])
            in_axis = True
            exclusions.add(gpr.name)
```

Please let me know if there are any changes needed. Thanks!

Labels:
name: Bug
name: Groupby
name: Warnings
description: Warnings that appear or should be added to pandas

Comments:
The failures here don't look related, but I'm not seeing them fail in other PRs. @mroeschke - have you seen `test_apply_raw_float_frame_lambda` fail in other PRs recently?
Thanks @sanggon6107 

Hmm interesting, no I haven't seen that test fail recently. I wonder if it's only happening on the 2.3.x branch for some reason
Fix crosstab(aggfunc='skew') bug
State: closed

Fix `IndexError` in `crosstab` with `aggfunc=‘skew’`.

* Check if table is empty before accessing last row in `_normalize` function in `pandas/core/reshape/pivot.py`.
* Skip normalization and return empty table if it is.
* Add test case in `pandas/tests/reshape/test_crosstab.py` for `aggfunc=‘skew’`.
* Ensure test case doesn’t raise `IndexError`.



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: Don't ignore errors when casting dtype in Series constructor
State: closed

- [ ] closes #60728
- [ ] [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.

In the constructor for `Series`, when the input data is another `Series` with a different `dtype` than the one specified in the constructor, the dtype conversion currently doesn't throw errors and silently sets the wrong dtype.
```
>>> example = pd.Series(
...     pd.Series([pd.NaT], dtype="datetime64[ns]"), dtype="timedelta64[ns]"
... )
>>> print(example.dtype)
datetime64[ns]
```


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

Comments:
Thanks again @snitish 
With this PR, this now raises:

    pd.Series([1.5], dtype="int64")

While perhaps we want to do this in the future, I think it can have a large impact and we definitely should not do it without proper deprecation. Ref: https://github.com/pandas-dev/pandas/issues/60728#issuecomment-2628496847
Ah, ignore me, that line always raised. I confused it with

    pd.Series(pd.Series([1.5], dtype="float64"), dtype="int64")

which still gives `int64` dtype as before.