BrandonFors/pandas-github-issues huggingface dataset:
DOC: remove links to deprecated methods
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 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: Deprecate
description: Functionality to remove in pandas

Comments:
@phofl no
this is fine. ty @guoci
TYP: Make temporary variables in pandas/__init__.py private
State: closed

Tiny step towards #39813 (`pyright --ignoreexternal --verifytypes pandas`) the relevant changes are in `pandas/__init__.py` and `pandas/_config/config.py` (private but `get_option`, ... uses the annotated wrapper).

I didn't plan to do the second commit (seemingly unrelated changes) but it seems that the first commit disturbed mypy's slumber (probably a few more cases that used the un-annotated wrapper?). I'm not very confident in the changes from the second commit (types for cython/c functions).

Labels:
name: Typing
description: type annotations, mypy/pyright type checking

Comments:
Hello @twoertwein! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:



There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2022-05-06 23:21:07 UTC
changes to `pandas/__init__.py` look fine (these could be separate PR if you want).
> changes to `pandas/__init__.py` look fine (these could be separate PR if you want).

I kept the simply changes in this PR and will later open a new PR for the remaining changes.
@jreback green
DOC: indicate that `month_name` and `day_name` also applies to Series
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 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:
<details><summary>Screenshots from local docs build</summary>

![Screen Shot 2022-04-08 at 9 18 31 AM](https://user-images.githubusercontent.com/247555/162454615-fad5b7d3-eab3-4ed3-843a-5439a1015153.png)

![Screen Shot 2022-04-08 at 9 18 13 AM](https://user-images.githubusercontent.com/247555/162454618-8d2f4aa8-592a-400e-babb-0ff3d2dcd4c9.png)

![Screen Shot 2022-04-08 at 9 18 04 AM](https://user-images.githubusercontent.com/247555/162454619-767b8eb6-2fc0-4704-8a94-275d73697f0d.png)

![Screen Shot 2022-04-08 at 9 18 37 AM](https://user-images.githubusercontent.com/247555/162454608-bcfe81c1-33af-4d5e-ac7f-5545fdb48577.png)

</details>
thanks @tswast 
@meeseeksdev backport 1.4.x
Something went wrong ... Please have a look at my logs.
BUG: isin casting to float64 for unsigned int and list
State: closed

- [x] closes #46485 (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 an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

The argument is cast to int64 which leads to an upcast later on -> to avoid this we can either use object-dtype for int or implement some casting logic which casts values to unsigned if possible

Labels:
name: Bug
name: Regression
description: Functionality that used to work in a prior pandas version
name: Algos
description: Non-arithmetic algos: value_counts, factorize, sorting, isin, clip, shift, diff

Comments:
looks fine. cc @jbrockmendel if any 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 @phofl
REGR: read_fwf raising ValueError when widths was specified with usecols
State: closed

- [x] closes #46580 (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 an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Regression
description: Functionality that used to work in a prior pandas version
name: IO Fixed Width
description: read_fwf

Comments:
thanks @phofl 
@meeseeksdev backport 1.4.x
Something went wrong ... Please have a look at my logs.
CI fix-ci-isocalendar
State: closed

Fix failing CI check

https://github.com/pandas-dev/pandas/runs/5874948094?check_suite_focus=true

probably caused by #46674

Labels:
name: Docs

Comments:
oh wow i guess that PR really did have an issue

merge when ready
OK thanks, merging then as this at least fixes the `Code Checks / Docstring and typing validation` job
Thanks for the quick fix!
@meeseeksdev backport 1.4.x
BUG: Series.replace with to_replace dict and value=None, nonsensical error message
State: closed

- [x] closes #46004
- [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 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: Series
description: Series data structure
name: replace
description: replace method
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.
> * [x]  closes [BUG: Series.replace with to_replace dict and value=None, nonsensical error message #46004](https://github.com/pandas-dev/pandas/issues/46004)
> * [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 an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Hi there, just curious if this issue still persist. I seem to be getting the same error with series.replace. Could anyone enlighten me if there is a version that would have resolved this?

Thank you!
ENH: implement non-nano Timedelta scalar
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 an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Not user-exposed.  This is just enough to allow us to have non-nano TimedeltaArray.

asvs for tslibs.timedelta unchanged


Labels:
name: Timedelta
description: Timedelta data type
name: Non-Nano
description: datetime64/timedelta64 with non-nanosecond resolution

Comments:
@WillAyd thoughts on troubleshooting non-Mac build failures at import-time `ImportError: [...]/pandas/_libs/tslibs/timedeltas.cpython-38-x86_64-linux-gnu.so: undefined symbol: pandas_datetime_to_datetimestruct`

So far i've determined that yelling "but it isn't undefined" at the screen doesn't help.
I think you need to modify setup.py so that timedeltas includes the header file np_datetime.h during compilation. 
Err sorry undefined symbol is a runtime error, so not a matter of include but rather a linkage error. Try adding `"sources": ["pandas/_libs/tslibs/src/datetime/np_datetime.c"],` in setup.py to the appropriate timedeltas.pyx entry
OK, adding np_datetime.c in setup.py for timedeltas's "sources" tentatively helps
@jreback gentle ping here and #46397, lots more to do along both lines
Fix a few test failures on big-endian systems
State: closed

These are all due to tests expecting little-endian dtypes, where in fact the endianness of the dtype is that of the host.

- [ ] closes #xxxx (Replace xxxx with the Github issue number) **No issue filed**
- [ ] [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 **Not applicable; fixes some tests on big-endian platforms**
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] 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: Compat
description: pandas objects compatability with Numpy or Python functions

Comments:
The force push was to remove a stray `from sys import byteorder` left over from when I rebased this from `v1.3.5` to `main`.
DOC: generate docs for the `Series.dt.isocalendar()` method.
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 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:
Screenshots of successfully built docs:

![weekofyear docs linking to isocalendar docs](https://user-images.githubusercontent.com/247555/162068649-857308c5-26ab-49ad-bd80-3fe31ff397f8.png)

![isocalendar docs](https://user-images.githubusercontent.com/247555/162068724-e89c06bd-9fb7-4640-a5d2-a81251accab2.png)


![Series index, showing link to isocalendar docs](https://user-images.githubusercontent.com/247555/162068677-1338417f-5267-4f6c-b7de-2767eed4477f.png)


hmm can you rebase on master, i think the doc build was borked previous.
thanks @tswast something odd on doc CI but your change is orthogonal.
@meeseeksdev backport 1.4.x
Something went wrong ... Please have a look at my logs.
Test added IntervalIndex_get_indexer_non_unique
State: closed

- [x] closes #30178 
- [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 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: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Period
description: Period data type
name: Interval
description: Interval data type
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 you'd like to continue, please merge in main, address the review, and we can reopen.
Allow using datetime64[ns, UTC] in IntervalDtype
State: closed

The current regexp doesn't allow the use of comma in the interval `subtype`, which means this statement fails
```
pd.IntervalIndex.from_arrays([1, 2], [2, 3], dtype='interval[datetime64[ns, UTC], right]')
```
with `TypeError: data type 'interval[datetime64[ns, UTC], right]' not understood`

The proposed change allows the use of comma inside square brackets in the `subtype`.


Labels:
name: Datetime
description: Datetime data dtype
name: Interval
description: Interval data type
name: Stale

Comments:
Hello @helgehatt! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:



There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2022-04-06 13:37:04 UTC
Thanks @helgehatt for the PR.

> The current regexp doesn't allow the use of comma in the interval `subtype`, which means this statement fails

If there is no existing issue for this, can you open one.

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 @helgehatt for the PR.
> 
> > The current regexp doesn't allow the use of comma in the interval `subtype`, which means this statement fails
> 
> If there is no existing issue for this, can you open one.

opened #46999

closing this as stale.
BUG: Fix infinite recursion loop when pivot of IntervalTree is ±inf
State: closed

When the pivot of an IntervalTree becomes ±inf the construction of the
IntervalTree comes to an infinite loop recursion.  This patch tries to fix that
by catching those cases and set the pivot to a reasonable value.

- [x] closes #46658 
- [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/v1.5.0.rst` file if fixing a bug or adding a new feature.


Labels:
name: Bug
name: Interval
description: Interval data type

Comments:
looks good. if you make non-draft can merge.
> looks good. if you make non-draft can merge.

Please also see my [comment to the issue](https://github.com/pandas-dev/pandas/issues/46658#issuecomment-1091352600). I am in particular stuck with what to do about the CI failure.
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.
> 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.

Skipping now the newly introduced tests on 32-bit like other tests of `test_interval_tree.py`.
cc @mroeschke when you are good
Thanks @johannes-mueller
CI/DOC: pin pydata-sphinx-theme to 0.8.0
State: closed

Temporary fix for https://github.com/pandas-dev/pandas/issues/46615

Labels:
name: Docs

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 1.4.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 cd1ab27f9289613ae851e540a842600bcce4bb98
```

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

```
git commit -am 'Backport PR #46663: CI/DOC: pin pydata-sphinx-theme to 0.8.0'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-46663-on-1.4.x
```

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

> "Backport PR #46663 on branch 1.4.x (CI/DOC: pin pydata-sphinx-theme to 0.8.0)"

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).
                
Thanks @jorisvandenbossche
I'll do the manual backport for now so that we don't have the issue on 1.4.3

(since I keep the doc build container around just in case and did the version change manually and rebuilt the docs rather than updating the release scripts)
TST: added test for joining dataframes with MultiIndex containing dates
State: closed

- [X] closes #33692 
- [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 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: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode

Comments:
Thanks @dospix
BUG: df.nsmallest get wrong results when NaN in the sorting column
State: closed

- [x] closes #46589
- [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).
- [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: Numeric Operations
description: Arithmetic, Comparison, and Logical operations

Comments:
Should this pr be recorded in 1.4.3 whatsnew? I see your 1.4.3 tag (instead of 1.5) on this issue. @simonjayhawkins 
Yes, this should move to 1.4.3
thanks @GYHHAHA 
@meeseeksdev backport 1.4.x
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting.
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting.
@meeseeksdev backport 1.4.x
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting.
TST: add validation checks on levels keyword from pd.concat
State: closed

- [x] closes #46653
- [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).
- [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: Reshaping
description: Concat, Merge/Join, Stack/Unstack, Explode
name: Error Reporting
description: Incorrect or improved errors from pandas

Comments:
Hello @GYHHAHA! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:





There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2022-04-06 20:35:42 UTC
thanks @GYHHAHA very nice!
DOC: fix SA04 errors flagged by validate_docstrings.py and add SA04 t…
State: closed

- [x] closes #25337
- [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).
- [NA] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Many of the SA04 reported in #25337 are already fixed, but there were two outstanding SA04 errors reported by valdiate_docstrings.py on main. So, I fixed those and added 'SA04' to the code_checks.py as per #25337


Labels:
name: Docs

Comments:
Thanks @dataxerik
DOC: clarified read_csv example
State: closed

* Simple clarification to the read_csv/read_fwf docs so that the example actually loads data into a dataframe.


Labels:

Comments:
I wanted to move the User Guide reference down to the examples section similar to the [read_html docs](https://github.com/pandas-dev/pandas/blob/main/pandas/io/html.py#L1095-L1098) but couldn't get it to build correctly locally.
This is how it’s done in near every other documentation page for Pandas. I’m disappointed that we can’t merge a disambiguating, net positive change in arguably the most important docs page for pandas.
Just an arbitrary page:

https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.sum.html

We are returning the result.

The actual issue here is, that the example is not checked
BUG/TST/DOC: added finalize to melt, GH28283
State: closed

Progress towards #28283

This PR gives the `melt` method the ability to propagate metadata using `__finalize__`.

- [ ] xref #28283
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests)
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added an entry in the latest `doc/source/whatsnew/v1.5.0.rst` file

Contributors:
- [Edward Huang](https://github.com/edwhuang23)
- [Solomon Song](https://github.com/songsol1)

Labels:
name: metadata
description: _metadata, .attrs

Comments:
very nice @edwhuang23 

also ok to do a few more methods in a PR.
CI/DOC: Unpin jinja2
State: closed

- [x] closes #46514 (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 an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Should be closed by https://github.com/jupyter/nbconvert/pull/1737; we'll see if CI agrees. Also specifies `nbconvert>=6.4.5`; this is the most recent version of nbconvert but because this is only for dev I think it's okay.

Labels:
name: Docs
name: CI
description: Continuous Integration
name: Dependencies
description: Required and optional dependencies

Comments:
@meeseeksdev backport 1.4.x
thanks @rhshadrach 
Something went wrong ... Please have a look at my logs.