BrandonFors/pandas-github-issues huggingface dataset:
Enhanced numeric.py to process hexadecimal,decimal,binary formats(0x 0o 0b…)
State: closed


- [x] closes #59207 (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 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.
Backport PR #59939 on branch 2.3.x (CI: Run jobs on 2.3.x branch)
State: closed

Backport PR #59939: CI: Run jobs on 2.3.x branch

Labels:
name: CI
description: Continuous Integration

Comments:
CI jobs are at least being triggered now. They are still failing because of mamba issues, which is being fixed with the backport in https://github.com/pandas-dev/pandas/pull/59936
CI: Run jobs on 2.3.x branch
State: closed

Like https://github.com/pandas-dev/pandas/pull/56664 for 2.2.x

Labels:
name: CI
description: Continuous Integration

Comments:
I suppose we could also directly merge it into the 2.3.x branch? But https://github.com/pandas-dev/pandas/pull/56664 first merged it into main and then backported it, so going to follow that same process here.

Merging, so it can actually be tested if it is working when backported
Handling conversion of empty categorical with dtype_backend='pyarrow'
State: closed

Handling the case where conversion of empty categorical series with specified dtype_backend='pyarrow' in convert_dtypes function results in 1) an error (when there are no defined categories) or 2) in null[pyarrow] dtype (when there are some defined categories).

- [x] Tests added and passed
- [x] Closes #59934 


Labels:
name: Bug
name: Categorical
description: Categorical Data Type
name: Stale

Comments:
Here's the new PR:
https://github.com/pandas-dev/pandas/pull/59952
@veljanin - please do not open a new PR, just push commits to this PR branch.
All changes should be in place now...
@veljanin - I think changes look good, can you merge main and resolve the conflict.
just added skip_if_no decorator to both tests
@veljanin - the CI failures are related and need to be addressed.
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 as stale. @veljanin - if you'd like to continue, address the above comments and we're happy to reopen!
BUG: fix html float display
State: closed

Part of #59876
- [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/v3.0.0.rst` file if fixing a bug or adding a new feature.

Fixes:
- Updated :meth:`DataFrame._repr_html_` to pass the current float format option from :func:`get_option("display.float_format")` to :class:`DataFrameFormatter`, ensuring that the HTML output respects the configured float formatting.



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

Comments:
Thanks @saldanhad 
Thanks for your help in formatting the tests @mroeschke
Include Python.h first
State: closed

Followup from https://github.com/pandas-dev/pandas/pull/59906#issuecomment-2384118611
/CC @WillAyd

Move `# include <Python.h>` to a separate include block to force `clang-format` to keep the order and it as first include.

Labels:
name: Refactor
description: Internal refactoring of code
name: Build
description: Library building on various platforms

Comments:
Looks good. Is there a clang-format argument we can pass or set to prevent the reorder?
> Looks good. Is there a clang-format argument we can pass or set to prevent the reorder?

There is [`SortIncludes: Never`](https://clang.llvm.org/docs/ClangFormatStyleOptions.html#sortincludes). I'm just not sure that's really necessary. Include sorting in itself is probably desirable. It's just the preference to put the `Python.h` includes at the top. As long as they are in a separate include block, that shouldn't be an issue.
Great thanks @cdce8p
DOC: fix docstrings for multiple api.types methods
State: closed

Part of #58577

Fixes :
 ```
        -i "pandas.api.types.is_re PR07,SA01" \
        -i "pandas.api.types.is_named_tuple PR07,SA01" \
        -i "pandas.api.types.is_hashable PR01,RT03,SA01" \
        -i "pandas.api.types.is_file_like PR07,SA01" \
        -i "pandas.api.types.is_dict_like PR07,SA01" \
```

Labels:
name: Docs

Comments:
Thanks @saldanhad
CI: Pin micromamba to 1.x
State: closed

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: CI
description: Continuous Integration

Comments:
Merging to restore the CI.
@jorisvandenbossche @WillAyd @lithomas1 - do we want to backport this? I can do so if desired.
Most likely - I'll take a look when I give the branch another pass. Thanks!
@MeeseeksDev backport to 2.3.x
CI: fix wrong syntax in CI env yml files (mamba 2.0 compat)
State: closed

All CI is failing with the new mamba 2.0 release. But it seems this is because we had invalid syntax (pip extras syntax) in our environment files, where mamba now fails on (previously used conda for parsing the yml files).


Labels:
name: CI
description: Continuous Integration

Comments:
It seems like there a few issues with mamba 2.0 with windows (https://github.com/mamba-org/setup-micromamba/issues/227) and the `list` command (https://github.com/mamba-org/setup-micromamba/issues/225) that we're also seeing here.

We may just need to pin the mamba version
I opened #59912 - planning to merge as soon as that's green. We can then use this to unpin once upstream is fixed.
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 @jorisvandenbossche 
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 de4eaf8b2e7c6b840dbd0198d8c3edf5eaf5afff
```

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

```
git commit -am 'Backport PR #59910: CI: fix wrong syntax in CI env yml files (mamba 2.0 compat)'
```

4. Push to a named branch:

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

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

> "Backport PR #59910 on branch 2.3.x (CI: fix wrong syntax in CI env yml files (mamba 2.0 compat))"

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).
                
Manual backport -> https://github.com/pandas-dev/pandas/pull/60175
ENH: set __module__ for Dtype and Index classes
State: closed

Modified top-level name object for all Types class in the Dtype module by importing the set module decorator and decorating the class. Tested the modification by adding an assert statement to the already existing test_set_module test function

- [x] xref #55178
- [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.


Labels:
name: Output-Formatting
description: __repr__ of pandas objects, to_string
name: Sprints
description: Sprint Pull Requests

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.
BUG: pd.eval with engine="numexpr" fails with float division
State: closed

This PR tries to address the division issue, such as `pd.eval("1/2", engine="numexpr")` giving 0.0.

The cause could probably be [this code](https://github.com/pandas-dev/pandas/issues/59736#issuecomment-2378776494). Not sure if this fix is correct. Reviews from maintainers are appreciated.

- [x] related to #59736 (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: expressions
description: pd.eval, query

Comments:
> Looks OK could you add a whatsnew note to `v3.0.0.rst`?

Added.
Thanks @yuanx749
BLD: Fix armv7 build
State: closed

- [x] closes #59905
- [ ] [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: Build
description: Library building on various platforms
name: ARM
description: aarch64 architecture

Comments:
CI should be fixed - merge main to kickoff the builds.
Great thanks for the contribution @cdce8p 

If you are interesting in further contributions, it might be a nice follow up to check all of the files we have and make sure that the Python include / macro always comes first. Probably worth turning off the clang-format feature that reorders includes to ensure that
> Great thanks for the contribution @cdce8p
> 
> If you are interesting in further contributions, it might be a nice follow up to check all of the files we have and make sure that the Python include / macro always comes first. Probably worth turning off the clang-format feature that reorders includes to ensure that

I might be able to take a look at that. No promises though 😅

@WillAyd What is the process to get this fix backproted to `2.2.x` / `2.3.x`? Should I open a new PR targeting the corresponding branches? Tbh this is currently one of the blocking items adopting the new release and subsequently being reading for Python 3.13.
So the scope of this is that it prevents running pandas on 3.13 on musl platforms right? 

The 2.2 branch I think is closed at this point. We are in the process of backporting a ton of things to 2.3, but I think also want to be very cognizant of what else goes there, because we have already spent a ton of time on that with very limited resources.

@lithomas1 @jorisvandenbossche @rhshadrach might also have opinions
> So the scope of this is that it prevents running pandas on 3.13 on musl platforms right?

It prevent building pandas `>=2.2.0` on musl with I believe all Python versions. _I did the tests with 3.12 but the last working release `2.1.4` isn't compatible with 3.13 in the first place._
Given that this is a tiny diff, lets at least backport this to 2.3.x
@MeeseeksDev backport to 2.3.x
> It prevent building pandas `>=2.2.0` on musl with I believe all Python versions.

If that is the case, would it be good to add a note about this in the 2.3.0 whatsnew file?
ENH: Improve error mesage verbosity in string accessor
State: closed

- [x] closes #59659  (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.

Continued stale PR: #59649

Labels:
name: Enhancement
name: Error Reporting
description: Incorrect or improved errors from pandas
name: Strings
description: String extension data type and string data

Comments:
@rhshadrach - could you take a look at this? thanks
I think this looks good, but the CI has many unrelated failures. I'd like to get those resolved before merging PRs.
CI is fixed, can you merge main.
@rhshadrach - CI looks good. Thanks
Thanks @KevsterAmp
DOC: fix RT03, ES01 for pandas.core.groupby.SeriesGroupBy.agg and pandas.core.groupby.SeriesGroupBy.aggregate
State: closed

fixes

```
pandas.core.groupby.SeriesGroupBy.agg RT03, ES01
pandas.core.groupby.SeriesGroupBy.aggregate RT03, ES01
```

Labels:
name: Docs

Comments:
Thanks @tuhinsharma121
DOC: Recommend conda from miniforge for contributing environment
State: closed

Originally, mamba was suggested as a conda alternative because the mamba solver was faster than the old conda solver when creating environments. Now that conda uses `libmamba` as the default solver, I think we can recommend using `conda` again for development environments

Labels:
name: Docs

Comments:
Does conda use conda-forge as the default channel now?
> Does conda use conda-forge as the default channel now?

When installing `miniforge` (which is recommended in our docs), `conda-forge` will be the default channel
CI/TST: Check for tzset in set_timezone
State: closed

Appears the ARM tests are failing because `tzset` is not available. This API is limited to certain platform so we should be checking if we can set a tz in the first place

Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: CI
description: Continuous Integration
name: Timezones
description: Timezone data dtype
name: ARM
description: aarch64 architecture

Comments:
Looks like the arm job is passing now so merging
@MeeseeksDev backport to 2.3.x
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 b9488218ae27b70d1669a932ab16e8ce5a257cf0
```

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

```
git commit -am 'Backport PR #59893: CI/TST: Check for tzset in set_timezone'
```

4. Push to a named branch:

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

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

> "Backport PR #59893 on branch 2.3.x (CI/TST: Check for tzset in set_timezone)"

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).
                
Manual backport in https://github.com/pandas-dev/pandas/pull/59941
Fixed #59592
State: closed

Don't know exactly .that does this work this the first time. I am contributing. Sorry for the mistake

- [ ] 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 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: Refactor _create_delegator_method using functools
State: closed

* Refactoring `_create_delegator_method` using `functools`, partially fixes the docstrings for below under #59592 and fixes #59783 :
```
        -i "pandas.Series.cat.add_categories PR01,PR02" \
        -i "pandas.Series.cat.as_ordered PR01" \
        -i "pandas.Series.cat.as_unordered PR01" \
        -i "pandas.Series.cat.remove_categories PR01,PR02" \
        -i "pandas.Series.cat.remove_unused_categories PR01" \
        -i "pandas.Series.cat.rename_categories PR01,PR02" \
        -i "pandas.Series.cat.reorder_categories PR01,PR02" \
        -i "pandas.Series.cat.set_categories PR01,PR02" \
```
```
        -i "pandas.Series.dt.to_period PR01,PR02" \
        -i "pandas.Series.dt.as_unit PR01,PR02" \
        -i "pandas.Series.dt.ceil PR01,PR02" \
        -i "pandas.Series.dt.day_name PR01,PR02" \
        -i "pandas.Series.dt.floor PR01,PR02" \
        -i "pandas.Series.dt.month_name PR01,PR02" \
        -i "pandas.Series.dt.normalize PR01" \
        -i "pandas.Series.dt.round PR01,PR02" \
        -i "pandas.Series.dt.strftime PR01,PR02" \
        -i "pandas.Series.dt.total_seconds PR01" \
        -i "pandas.Series.dt.tz_convert PR01,PR02" \
        -i "pandas.Series.dt.tz_localize PR01,PR02" \
```




Labels:
name: Docs
name: Accessors
description: accessor registration mechanism (not .str, .dt, .cat)

Comments:
ping @rhshadrach , @mroeschke for review. 
/preview
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/59878/
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/59878/
Just inquiring to see if i've missed to implement any changes here ? @mroeschke 
Thanks @saldanhad
TST: update frame method quantile tests
State: closed

xref https://github.com/pandas-dev/pandas/issues/54792

(this doesn't need to be backported to 2.3.x because we only fixed it recently to properly preserve the index dtype for empty results in https://github.com/pandas-dev/pandas/pull/59035)

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

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.
Fix Docstring Issues for pandas.Series.sparse.sp_values and pandas.Series.str.match (Issue #59592)
State: closed

This pull request addresses the following issues:

- Fixed docstring for pandas.Series.sparse.sp_values: ES01, SA01
- Fixed docstring for pandas.Series.str.match: ES01
- Removed the corresponding methods from the code_checks.sh script.

- [x] Part of #59592(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:

Comments:
pre-commit.ci autofix
@mroeschke I'm a beginner in open-source contributing and experiencing a CircleCI test failure on  `test-linux-arm` in my PR. Could someone please help me troubleshoot or provide more info on the error?
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: fix SA01, ES01 for pandas.errors.EmptyDataError
State: closed

related to #58063

fixes

```
pandas.errors.EmptyDataError SA01, ES01
```

Labels:
name: Docs

Comments:
Hi @tuhinsharma121, it would help if you could link your PR's to the issue to let others know and can avoid duplicated efforts. Thanks!
Thanks @tuhinsharma121
DOC: fix RT03, ES01 for pandas.core.groupby.DataFrameGroupBy.agg and pandas.core.groupby.DataFrameGroupBy.aggregate
State: closed

fixes

```
pandas.core.groupby.DataFrameGroupBy.agg RT03, ES01
pandas.core.groupby.DataFrameGroupBy.aggregate RT03, ES01
```

Labels:
name: Docs

Comments:
This is looking good to me, but we'll need to wait until the CI gets fixed in order to ensure the docs build correctly.
Thanks @tuhinsharma121
DOC: Fix inconsistent and incomplete documentation of `pandas.eval`
State: closed

- [x] closes #58338
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

This PR implements the suggested documentation improvements outlined in #58338:
- Covering the supported operators and functions to `pandas.eval`
- Reorganising and adding links to  `pandas.DataFrame.eval` and  `pandas.DataFrame.query` to have a consistent explanation of the `expr` parameters

Labels:
name: Docs
name: expressions
description: pd.eval, query

Comments:
Thanks @JonathanMarriott