BrandonFors/pandas-github-issues huggingface dataset:
TST: Add test for series str decode GH#22613
State: closed

- [ ] closes #22613  (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: Strings
description: String extension data type and string data

Comments:
Thanks @liang3zy22
REF: Remove side effects from importing Styler 2
State: closed

draft

Alongside this PR I would also recommend:

 - [ ] deprecating `Styler.from_custom_template` since it will be more featureful to create a class directly with specified new templates, and basically just as easy. Docs could be updated.

Labels:
name: Styler
description: conditional formatting using DataFrame.style
name: Stale

Comments:
@rhshadrach I created this versus your original PR, to remove some of the floating class attribute caches.

One or two things to clean up test wise but I think it preserves almost all functionality whilst achieving the import side effects changes.
Sounds good!
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.
Are you still working on this @attack68?
I looked at this yesterday coincidentally actually. Last I checked this works locally but I couldnt get the tests to pass online because they read a file and I guess there is something wrong with the paths. This was quite a good PR though just havent had time to push it over the edge.
Closing to clear the queue, but when you have time to come back to this feel free to reopen the PR
POC: Don't special case Python builtin and NumPy functions
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 PR is just to demonstrate the impact of #53425 on tests.

```
np.random.seed(26)
size = 100000
df = pd.DataFrame(
    {
        "a": 0,
        "b": np.random.random(size),
    }
)
gb = df.groupby("a")

# This PR
print(gb.agg("sum").iloc[0, 0])
# 50150.538337372185
print(gb.agg(np.sum).iloc[0, 0])
# 50150.53833737219

# main
print(gb.agg("sum").iloc[0, 0])
# 50150.538337372185
print(gb.agg(np.sum).iloc[0, 0])
# 50150.538337372185

Labels:
name: Apply
description: Apply, Aggregate, Transform, Map
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.
Closing in favor of #53974
Fixes the page rander Problem
State: closed

- [x] closes #53414  (Replace 53414 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:

Comments:
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/53423/
Oh, I forgot it 😯, I'm going to fix it 
i'm setting up the website  on the locally but when  i tried to fix the bullet notation the file where changes reflected which was not open it on the browser it simply download that file give me some solution. 
ok no worries - closing then until you solve your environment and get it building to free this up for others
okk no worry. i will fix it then work it .
DOC: Typo fix on subset data doc
State: closed

- [x] closes #53395
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

Labels:
name: Docs

Comments:
The first commit was attempting a push on the upstream. `Sanity Check` was my way of trying to prevent that. A simple git-reset would have sufficed.
BUG: Adds missing raises for numpy.timedelta64[M/Y] in pandas.Timedelta
State: closed

- [x] closes #52806
- [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 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: Non-Nano
description: datetime64/timedelta64 with non-nanosecond resolution

Comments:
- Uploading this draft to make sure I'm in the right direction.  
- Will add tests into if this`test_timedeltas.py` if appropriate.
- Let me know if I need to improve the raise message @mroeschke. 
Looking at the 3 failed tests:
1. `test_constructors.py::test_construction_out_of_bounds_td64ns`
2. `test_constructors.py::test_construction_out_of_bounds_td64s`
3.  `test_lib.py::TestMisc::test_fast_multiget_timedelta_resos`

My assumption is that the correct approach would be to alter tests to now expect a value error to be thrown but I'm a little unsure if the is the right mentality. 

I'm a little unsure of the best approach though, any guidance would appreciated. 
Went ahead and updated the test to reflect the newly added raise condition. 
Finally ready... thanks for the patience @mroeschke 
Anything else needed here? 
Thanks @mcgeestocks
DOC: add missing parameters to offsets classes: MonthEnd, MonthBegin, BusinessMonthEnd, and BusinessMonthBegin
State: closed

xref  #52431
Updated documentation for offsets classes. Added missing parameters and See Also section to MonthEnd, MonthBegin, BusinessMonthEnd, and BusinessMonthBegin.

Labels:
name: Docs

Comments:
@MarcoGorelli, could you please take a look at this pr?
DEPR: Series.first() and DataFrame.first()
State: closed

- [x] closes #45908
- [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.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

I don't know which "whatsnew" I need to edit (which version) 

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

Comments:
@MarcoGorelli I think the last failing test is not related to these changes.

I separated the test for `first()` on `test_finalize.py` thinking that it will make it easy to remove it when it is time.
Friendly ping again @MarcoGorelli - It looks green 

merging then, do you want to do a similar one for `last`?
> merging then, do you want to do a similar one for `last`?

Yes.. Thank you @MarcoGorelli.
BUG: series sum changes dtype uint64 to int64
State: closed

- [X] closes #53401 
- [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.

🚫Before
![image](https://github.com/pandas-dev/pandas/assets/61644078/0951c9e2-4513-4f64-b2e0-b4f949cc851e)


✅After changes
![image](https://github.com/pandas-dev/pandas/assets/61644078/3a719662-8142-4152-8525-268976252e42)


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

Comments:
Thanks, @srkds. 

This should be handled in `_get_dtype_max`, unless I'm missing something . You should also add tests for this and an entry in the v2.1 whatsnew.


I missed the `_get_dtype_max` method while checking the execution flow. Thanks for the suggestion 👍
Added test case and entry in `whatsnew` file.

Thanks!
Thanks @srkds 
Nice one, @srkds.
Thanks @topper-123 and @mroeschke for reviewing and merging.
I have made progress from contributing to docs fixing typos, then adding test cases, and now contributed a bug fix 🎉😀.
It wouldn't be possible without maintainers like you.
Looking forward to contributing more ❤.
Indentation fix
State: closed

- [ ] closes #53416  (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 your pr but this doesn't really address the issue - closing then to free the issue up for others

please try building the web page before pushing
closes the issue #49046
State: closed

- [ ] closes #49046  (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 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: Update release date for 2.0.2
State: closed

xref #52892

CI for 2.0.x should be fixed now. Planning to release on Monday, updating the date.

Labels:
name: Docs
name: Release

Comments:
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 2.0.x
git pull
```

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

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

```
git commit -am 'Backport PR #53413: DOC: Update release date for 2.0.2'
```

4. Push to a named branch:

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

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

> "Backport PR #53413 on branch 2.0.x (DOC: Update release date for 2.0.2)"

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).
                
@meeseeksdev backport 2.0.x
DEPR: Deprecate literal json string input to read_json
State: closed

- [X] closes #52271
- [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: IO JSON
description: read_json, to_json, json_normalize
name: Deprecate
description: Functionality to remove in pandas

Comments:
**Code Checks / Docstring validation, typing, and other manual pre-commit hooks (pull_request)** test failing seems to be unrelated to changes in my PR.

**Doc Build and Upload** seems to be failing because the CI test itself passes literal JSON strings to `read_json`. This doesn't seem like something that I can fix myself?


@mroeschke Would you be able to take a look at this PR and let me know if anything needs updating?
@mroeschke This PR should be ready for review!
@mroeschke This PR should be ready for review!
@mroeschke PR is ready for review. 

I believe I have addressed your concerns. From what I can tell, the test failures in Numpy Dev are not related to my PR
Could you merge in the main branch too?
@mroeschke Should be good to go now. 
Looks like some of the code checks are still failing in the CI
@mroeschke Code Checks / Docstring validation passing now. Docbuild and upload test failure doesn't appear to be associated with PR 
You may want to check usage of `read_json` in the the `doc/source` folder for the deprecated behavor. PRs should still pass the doc build
@mroeschke Pinging on green!
@mroeschke Should be good to go now!
Thanks @rmhowe425
`DataFrame.dictmap` - apply multiple column transforms simultaneously via a dict and `DataFrame.map`
State: closed

Adds a `dictmap` instance method to `DataFrame`, that allows callers to apply multiple column transforms simultaneously via a dict of column names and transform functions.

The specified columns are keyed in the dict passed to the method, and the values are the associated transforms. 

The transforms are applied via `DataFrame.map`, while the columns are concatenated along the columns axis.

The row index is unchanged, and the output has the same shape as before.

Example below:
```
>>> d = pd.DataFrame([[1,4,7],
...                   [2,5,8],
...                   [3,6,9]],
...                   columns=['x', 'y', 'z']
>>> df
   x  y  z
0  1  4  7
1  2  5  8
2  3  6  9
>>> df.dictmap({'x': lambda x: x ** 2,
                'z': lambda z: 1 - z/2})
   x  y    z
0  1  4 -2.5
1  4  5 -3.0
2  9  6 -3.5
```


Labels:

Comments:
-1 this is duplicative of assign

please open a feature request issue for discussion before a PR
> please open a feature request issue for discussion before a PR

OK, this isn't quite clear in your contributions guide.
TST: Adds test for date_range index comparison
State: closed

- [x] closes #19088
- [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.~

### Details:
Adds missing test from previously resolved issue: #19088 

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

Comments:
Thanks @mcgeestocks
PDEP6 implementation pt 2: eablock.setitem, eablock.putmask
State: closed

following on from #50626 

Labels:
name: API Design

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 @MarcoGorelli 
@MarcoGorelli do you have time/appetite to start enforcing the PDEP6 deprecation?

If not, is enforcing the deprecation as easy as switching the warnings to exceptions or is there more cleanup?
thanks for the ping! yup, I'll get to it - exciting to see it enforced!
> @MarcoGorelli do you have time/appetite to start enforcing the PDEP6 deprecation?

doing it today - sorry for the delay, been too caught up with other work projects, but some of them are winding down now
DOC: Check if the sphinx warning is caused by the label name
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:
@attack68 any idea what the problem can be? The doc raises a warning for the label it can't find, but only in 2.0.x, which is weird since the code doesn't seem to have changed. I guess it may be that we're using different versions of sphinx or an extension between `main` and `2.0.x`, but not sure exactly what's wrong.
Seems like the wrong label was the problem. Closing, since this is targeting the `2.0.x` branch, and will reopen to `main` and backport. No idea why the CI is unhappy in `2.0.x` and happy in `main`, I guess it's about the version of dependencies, but worth fixing it everywhere.
fix documentation build error in basics.rst
State: closed

DOC: fix documentation build error in basics.rst based on #53354

building with `python make.py --single user_guide/basics.rst`
now works without issues

- [ ] closes #53354 
- [ ] [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 @DominikBerger01
DOC: Adjust build command for building with meson
State: closed

Change default command to show verbose output, as discussed during the dev call.

Otherwise, it might be confusing for users when the import hangs and their CPU goes to 100% during the rebuild step.

cc @ngoldbaum
- [ ] 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:
Tested this and now I get verbose output when importing pandas triggers meson to do things.
BUG: read_csv with dtype=bool[pyarrow]
State: closed

- [ ] closes #53390 (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 CSV
description: read_csv, to_csv
name: Arrow
description: pyarrow functionality

Comments:
Ah sorry, I forgot the 2.0.2 release was today.

Can you move the whatsnew note to 2.0.3?
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 1a57d153732b888f98b42d87f590952b262641c3
```

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

```
git commit -am 'Backport PR #53391: BUG: read_csv with dtype=bool[pyarrow]'
```

4. Push to a named branch:

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

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

> "Backport PR #53391 on branch 2.0.x (BUG: read_csv with dtype=bool[pyarrow])"

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).
TST: Add test for pandas on sys.getsizeof GH#21758
State: closed

- [ ] closes #21758 (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

Comments:
Thanks @liang3zy22