BrandonFors/pandas-github-issues huggingface dataset:
BUG: str.split for ArrowDtype with pat=None
State: closed

- [x] closes #56271 (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: Strings
description: String extension data type and string data
name: Arrow
description: pyarrow functionality

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.1.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 2718b4e702fa7f0698ade48472497fd0afb2398e
```

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

```
git commit -am 'Backport PR #56332: BUG: str.split for ArrowDtype with pat=None'
```

4. Push to a named branch:

```
git push YOURFORK 2.1.x:auto-backport-of-pr-56332-on-2.1.x
```

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

> "Backport PR #56332 on branch 2.1.x (BUG: str.split for ArrowDtype with pat=None)"

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).
[pre-commit.ci] pre-commit autoupdate
State: closed

<!--pre-commit.ci start-->
updates:
- [github.com/hauntsaninja/black-pre-commit-mirror: 23.10.1 → 23.11.0](https://github.com/hauntsaninja/black-pre-commit-mirror/compare/23.10.1...23.11.0)
- [github.com/astral-sh/ruff-pre-commit: v0.1.4 → v0.1.6](https://github.com/astral-sh/ruff-pre-commit/compare/v0.1.4...v0.1.6)
- [github.com/MarcoGorelli/cython-lint: v0.15.0 → v0.16.0](https://github.com/MarcoGorelli/cython-lint/compare/v0.15.0...v0.16.0)
- [github.com/sphinx-contrib/sphinx-lint: v0.8.1 → v0.9.0](https://github.com/sphinx-contrib/sphinx-lint/compare/v0.8.1...v0.9.0)
- [github.com/pre-commit/mirrors-clang-format: v17.0.4 → v17.0.6](https://github.com/pre-commit/mirrors-clang-format/compare/v17.0.4...v17.0.6)
<!--pre-commit.ci end-->

Labels:
name: Code Style
description: Code style, linting, code_checks

Comments:
Bumped and green
thanks @mroeschke.
BUG: Fixed bug when creating new column with missing values when setting a single string value
State: closed

- [ ] closes #56204 (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: Strings
description: String extension data type and string data
name: Arrow
description: pyarrow functionality

Comments:
thanks for your reviews! have updated
Just tracked down an old branch where past-me was trying to get rid of infer_fill_value.  The only recoverable bit of that branch looks like it would go just before L1880 in indexing.py

```
                        elif not is_list_like(value):
                            # Find our empty_value dtype by constructing an array
                            #  from our value and doing a .take on it
                            arr = sanitize_array(value, Index(range(1)), copy=False)
                            taker = -1 * np.ones(len(self.obj), dtype=np.intp)
                            empty_value = algos.take_nd(arr, taker)
                            self.obj[key] = empty_value
```

would that solve the issue here robustly?  i like past-me's idea of using sanitize_array rather than yet-another constructor-esque function
That would also avoid the warning when expanding column-wise:

main:
```python
In [1]: df = pd.DataFrame({'a': [.1, .2], 'b': [.3, .4]})

In [2]: df.loc[1, 'c'] = True
<ipython-input-2-d3d953ae007a>:1: FutureWarning: Setting an item of incompatible dtype is deprecated and will raise in a future error of pandas. Value 'True' has dtype incompatible with float64, please explicitly cast to a compatible dtype first.
  df.loc[1, 'c'] = True

In [3]: df
Out[3]: 
     a    b     c
0  0.1  0.3   NaN
1  0.2  0.4  True

In [4]: df.dtypes
Out[4]: 
a    float64
b    float64
c     object
dtype: object
```
here:
```python
In [1]: df = pd.DataFrame({'a': [.1, .2], 'b': [.3, .4]})

In [2]: df.loc[1, 'c'] = True

In [3]: df
Out[3]: 
     a    b     c
0  0.1  0.3   NaN
1  0.2  0.4  True

In [4]: df.dtypes
Out[4]: 
a    float64
b    float64
c     object
dtype: object
```
thanks for your reviews! merging then
DOC: Move whatsnew
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:
#55619 didn't make it into 2.1.2 and I forgot about it for 2.1.3.

Just merged #55705 to backport it for 2.1.4, though.
pre-commit.ci autofix
Thanks @lithomas1
BUG / CoW: ensure ser[...] (indexing with Ellipsis) returns new object
State: closed

Small corner cases that I noticed where we are still unconditionally returning `self` instead of a shallow copy. 

Labels:
name: Bug
name: Copy / view semantics

Comments:
thx
> That was an actual bug, correct?

Yes, in the CoW mode (I left the default mode intact, although in theory that could also have returns a new object, like `:` does)
DOC: Add whatsnew for concat regression
State: closed

- [ ] xref #53641  (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:
Draft until I fix CI on the other PR.
self-merging since this seems small enough.
Backport PR #53641: BUG: `pd.concat` dataframes with different dateti…
State: closed

…me64 resolutions

- [ ] 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.


Adding whatsnew in separate PR.

Labels:
name: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Regression
description: Functionality that used to work in a prior pandas version
name: Non-Nano
description: datetime64/timedelta64 with non-nanosecond resolution

Comments:
Doesn't backport cleanly closing
BUG: merge should upcast to highest resolution
State: closed

- [ ] closes #55212  (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: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Stale
name: Non-Nano
description: datetime64/timedelta64 with non-nanosecond resolution

Comments:
@jbrockmendel 

This only gets some of the cases.

I think this misses when we take everything from the left join col.
Any idea where to handle the upcasting then?
> I think this misses when we take everything from the left join col.  Any idea where to handle the upcasting then?

Do you have an example?  That'd save me some time in figuring out what code paths that case goes through
Sorry for the slow reply.

I think my changes here only fixed the result for outer/right merges. The tests that I've added that are failing are doing so for inner/left merges.

Here's a MRE.
```
t1 = '2023-09-01'
t2 = '2023-09-01 01:00:00'
t3 = '2023-09-01 01:30:00'
ds1 = pd.date_range(t1, t2, freq='30T')
ds2 = pd.date_range(t1, t3, freq='30T')
df1 = pd.DataFrame({
    'ds': ds1.astype('datetime64[us]'),
    'y1': range(len(ds1)),
})
df2 = pd.DataFrame({
    'ds': ds2.astype('datetime64[ns]'),
    'y2': range(len(ds2)),
})
# Changing this to outer/right makes it work
df3 = df1.merge(df2, on=['ds'], how='left') #will only convert df2 `ds` type to df1 `ds` type
df3.dtypes
```
The code change looks good to me.  The test change looks plausible but i haven't examined closely.
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.
Looks like this PR has gone stale and needs a rebase. Closing to clear the queue but feel free to reopen when you have time to circle back
BUG: df.to_csv() fails to a not-yet-created file when the path is fsspec-based (#55828)
State: closed

When specifying local to_csv file paths with the file scheme, Pandas will now create the file instead of raising an exception

- [✅ ] closes #55828 (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: IO Data
description: IO issues that don't fit into a more specific label
name: Stale

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 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.
REGR: Fix reading old pickles from pandas 1.3.5
State: closed

- [ ] closes #55137 (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: IO Pickle
description: read_pickle, to_pickle

Comments:
Huh, the pickle_compat route is even simpler.

I just re-routed ``new_block`` to go through ``_unpickle_block``.
Hopefully, that should be right.
Thanks so much for looking into this @lithomas1
DOC: Tidy docstring
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
- [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

Comments:
Thanks @smij720
Update broken-linkcheck.yml
State: closed

A Github Action to run the Sphinx linkcheck monthly to check link errors. If errors are found, the GIthub Action creates a new issue, (and delete the old one) reporting all the errors, and label as Docs and Good First Issue

- [X] closes #45409 (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:
@datapythonista , @mroeschke 
Can you test this on your own fork to see an example of an issue being created?
@mroeschke, this yaml file is not creating any issue in my repo.  The `create or update Linkcheck issue` step is showing these errors in my repo:
```
Error: HttpError: Resource not accessible by integration
Error: Request to create new issue failed
```
Is this related to any permission related problem ?

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: Start migration guide for Copy-on-Write
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: Copy / view semantics

Comments:
I think we should link from the FutureWarning to this section as well, but that can be a follow up
Add pot files for translating pandas documentation
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 will not be a PR for code contribution, but for translating documentation.
I would like to multilingualize pandas documentation by translating the pot files using a translation service called Crowdin.

According to @steppi, Crowdin will allow Scientific Python community to have a free enterprise account to serve as an umbrella account for managing translations of scientific Python projects.

By the way, I created these pot files using `sphinx-intl`, like https://github.com/sphinx-doc/sphinx-doc-translations .


Labels:

Comments:
I have opened an issue for discussion #56301 .
Thanks for the PR so far, but as mentioned this topic needs more discussion before proceeding with a PR so closing so the discussion can happen in the opened issue first
Assort IWYU Cleanups
State: closed

include-what-you-use is a relatively common tool for cleaning up includes. it helps to localize includes and identify unnecessary ones

It has a few rough edges that don't make it 100% compatible with our code base, so I'm not sure we can do this in CI. But here were a few cleanups I manually gleaned from the IWYU output that I think make sense

Labels:
name: Clean

Comments:
Thanks @WillAyd
BUG: Series(strings, dtype=ArrowDtype[timestamp]) raising
State: closed

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

Comments:
thx
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.1.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 59936dc142b9ae8c3946dc9048aac5c7e86e6341
```

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

```
git commit -am 'Backport PR #56294: BUG: Series(strings, dtype=ArrowDtype[timestamp]) raising'
```

4. Push to a named branch:

```
git push YOURFORK 2.1.x:auto-backport-of-pr-56294-on-2.1.x
```

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

> "Backport PR #56294 on branch 2.1.x (BUG: Series(strings, dtype=ArrowDtype[timestamp]) raising)"

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).
ENH: Make get_dummies return ea booleans for ea inputs
State: closed

- [ ] closes #56273 (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: ExtensionArray
description: Extending pandas with custom dtypes or arrays.

Comments:
cc @mroeschke this is green now
Thanks @phofl
Convert ArrowExtensionArray to proper NumPy dtype
State: closed

- [ ] closes #56285 (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.


As discussed on the other pr

Labels:
name: Arrow
description: pyarrow functionality

Comments:
cc @mroeschke 

this should be ready as well
DOC: Explicit how 'cond' is updated on 'where'
State: closed

This PR updates the section notes on `DataFrame.where(cond, other=nan, *, inplace=False, axis=None, level=None)` docstring.
Currently pandas isn't explicit on who is being updated when  `cond` is misaligned with `other`. Just made that explicit to avoid confusion.

Labels:
name: Stale

Comments:
@aureliobarbosa kindly link your PR to the GitHub issue
@samukweku  There is no open issue related to this PR. I found the problem and just tried to fix it directly through a PR because recently I did the same on CPython and there the instructions were clear that if it where very small contribution (typo, link, etc) it wasn't necessary to open an issue. 

I just added three words to definite a relation explicitly. Should I open a new issue?
Kindly ignore my comments . I'll let @pandas-dev/pandas-core team speak on this. @phofl @Dr-Irv 
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.
Allow c files in src/include for gitignore
State: closed

Projectile in emacs uses .gitignore to consider certain files are part of the project, so any of our extensions in the src/include subfolders were being excluded by our blanket rules on generated .c/.h files

I would imagine this has benefits for VSCode and other editors as well in terms of file discoverability and searching

Labels:
name: Code Style
description: Code style, linting, code_checks

Comments:
Thanks @WillAyd