BrandonFors/pandas-github-issues huggingface dataset:
WEB: Update versions json to fix version switcher in the docs
State: closed

- [X] xref https://github.com/pandas-dev/pandas/pull/48600#issuecomment-1252065060

CC: @phofl 

Labels:
name: Docs
name: Web
description: pandas website

Comments:
> So we don't need the full path?

The url is only used in the new version of the theme, and for what I saw the value is used directly in the href, so probably better without then I think.
I am asking because initially we had the full path:

```
    "switcher": {
         "json_url": "https://pandas.pydata.org/versions.json",
         "url_template": "https://pandas.pydata.org/{version}/",
         "json_url": "/versions.json",
         "version_match": switcher_version,
     },
```

but this is part of the conf.py, so the old versions of the docs can still access this, correct?

https://github.com/pandas-dev/pandas/pull/48285/files
Yes, everything in conf.py stays in the already rendered version of the docs, so it's not affecting the released versions, and we can't update it for them either.

Both will work, with and without the domain. But without will allow for example to test it in the new server without unintentionally going to the old one.
thx @datapythonista
REGR: TextIOWrapper raising an error in read_csv
State: closed

- [x] closes #48646
- [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.

If `TextIOWrapper.buffer` has some more unexpected surprises, it might be worth not to use this shortcut (use src instead of src.buffer). Or only have this shortcut when pandas opens the file (edit: I went for this approach).

Labels:
name: IO CSV
description: read_csv, to_csv

Comments:
Thanks @twoertwein
BUG: MultiIndex.set_levels raising when setting empty level
State: closed

- [x] closes #48636 (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: MultiIndex

Comments:
Thanks @phofl
DOC: Add release notes for 1.5.1
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.


cc @datapythonista can we push stuff again and create a 1.5.1 milestone? 


Labels:
name: Docs

Comments:
The release is not yet done, but I don't see a reason not to push to main. As far as I can tell only the release candidate was tricky, since it's when we branch from main. Also ok to backport to `1.5.x`, we already got the tag in place, so I guess any changes after the tag will be ignored in the conda-forge and macpython builds.

I created the 1.5.1 milestone and move all 1.5 PRs to it.
Thanks very much. Can move whatsnews over to then after this is merged. Great!
BUG: is_datetime64tz_dtype shortcut only for DatetimeTZDtype
State: closed

- [x] closes #34986 (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/v1.6.0.rst` file if fixing a bug or adding a new feature.


Labels:
name: Dtype Conversions
description: Unexpected or buggy dtype conversions
name: Timezones
description: Timezone data dtype
name: ExtensionArray
description: Extending pandas with custom dtypes or arrays.

Comments:
thx. @mroeschke
CI: Fix directory name for published prod docs
State: closed

- [X] xref #48211 

The job to publish the docs to our production server when a new tag is created worked mostly fine for the 1.5.0 release. The only thing is that the tag name is `v1.5.0`, while the docs had to be published to the `1.5.0` directory (without the heading `v`). Fixing this here, so docs are published to the right directory.

Labels:
name: Docs
name: CI
description: Continuous Integration

Comments:
I think we should backport for the 1.5.x releases
BUG: Fixed DataFrame.__repr__ Type Error when column dtype is np.record (GH 48526)
State: closed

- [x] closes #48526
- [x] [Tests added and passed]
- [x] All [code checks passed]
- [x] Added an entry in the latest `doc/source/whatsnew/v1.6.0.rst` file if fixing a bug or adding a new feature.


Labels:
name: Output-Formatting
description: __repr__ of pandas objects, to_string
name: Nested Data
description: Data where the values are collections (lists, sets, dicts, objects, etc.).
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.
> 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.

still interested
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.
@mroeschke 
Can we re-open the pull request? I merged the main branch and your first and second review comment were already considered: I moved the test to `pandas/tests/frame/test_repr_info.py` and also checked against `repr(df)`. I commented on your last review comment but never got an answer if my explanation was sufficient or not.
Thank you in advance.
Sure, reopened this pull request
@mroeschke 
It passes the CI tests, but there is some connection problem with codecov:
"['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 503 - upstream connect error or disconnect/reset before headers. reset reason: connection failure"
Thanks for sticking with this @RaphSku
DOC: Update documentation for date_range(), bdate_range(), and interval_range() to include timedelta as a possible data type for the freq parameter
State: closed

- [X] closes https://github.com/pandas-dev/pandas/issues/48460

This PR simply documents behavior that was already allowed, and was already properly documented on the underlying function `to_offset()`.

```
In [1]: import pandas as pd                                                                                                                                                          

In [2]: from datetime import date, timedelta                                                                                                                                         

In [3]: start = date(2022, 1, 1)                                                                                                                                                     

In [4]: end = date(2022, 1, 11)                                                                                                                                                      

In [5]: pd.date_range(start, end, freq=timedelta(days=2))                                                                                                                            
Out[5]: 
DatetimeIndex(['2022-01-01', '2022-01-03', '2022-01-05', '2022-01-07',
               '2022-01-09', '2022-01-11'],
              dtype='datetime64[ns]', freq='2D')

In [6]: pd.bdate_range(start, end, freq=timedelta(days=2))                                                                                                                           
Out[6]: 
DatetimeIndex(['2022-01-01', '2022-01-03', '2022-01-05', '2022-01-07',
               '2022-01-09', '2022-01-11'],
              dtype='datetime64[ns]', freq='2D')

In [7]: start = pd.Timestamp(start)                                                                                                                                  

In [8]: end = pd.Timestamp(end)                                                                                                                                     

In [9]: pd.interval_range(start, end, freq=timedelta(days=2))                                                                                                       
Out[9]: IntervalIndex([(2022-01-01, 2022-01-03], (2022-01-03, 2022-01-05], (2022-01-05, 2022-01-07], (2022-01-07, 2022-01-09], (2022-01-09, 2022-01-11]], dtype='interval[datetime64[ns], right]')
```

Labels:
name: Docs
name: Datetime
description: Datetime data dtype

Comments:
Thanks. Do we also have unit tests for these functions accepting timedelta inputs for `freq`?
Thanks @gandhis1 
@mroeschke I'm not sure why the linked issue is not closed automatically. Can you close it please?
Backport PR #48619 on branch 1.5.x (REGR: Loc.setitem with enlargement raises for nested data)
State: closed

Backport PR #48619: REGR: Loc.setitem with enlargement raises for nested data

Labels:
name: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Regression
description: Functionality that used to work in a prior pandas version
name: Nested Data
description: Data where the values are collections (lists, sets, dicts, objects, etc.).

Comments:
Cc @datapythonista 

I’ll be done for the day before the ci is through
CI: Get rid of some warnings
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: Warnings
description: Warnings that appear or should be added to pandas

Comments:
Thanks @phofl
DOC: Last changes to release notes for 1.5.0 release
State: closed

- [X] closes #48248

Updating date, clean up, and adding contributors to the 1.5.0 release. @pandas-dev/pandas-core I think this should be the last blocker for the 1.5.0 release. If merging anything else after this PR and before the release, please let me know.

Labels:
name: Docs

Comments:
https://github.com/pandas-dev/pandas/pull/48619

This one would be ready, but no big deal if we do for 1.5.1
I believe #48620 is all set to go. It's a somewhat substantial fix to a widespread performance regression, but I think it would be okay to wait for 1.5.1. Not a blocker in my opinion.
Thx @datapythonista
REGR: sort_value can not sort levels with non nas and nans
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.


cc @lukemanley 

open for suggestions if there is a more efficient way, but this raises right now while it did not before

Labels:
name: Regression
description: Functionality that used to work in a prior pandas version
name: MultiIndex

Comments:
#48495 handles this case (I just tested it). If we can merge #48495 I don't think we need this. 
Can you add this specific test too?
yep, added.
Thx, will keep open till the other is merged.
other pr was merged, so this is fixed
REGR/DOC: Docs left navbar broke
State: closed

- [x] closes #48605 (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.

cc @phofl 

Labels:
name: Bug
name: Docs
name: Regression
description: Functionality that used to work in a prior pandas version

Comments:
Pages opens with side navigation collapsed:

![image](https://user-images.githubusercontent.com/45562402/190912623-167f45ea-1d3b-4bc2-b625-65d90c0f8d19.png)

And expands correctly

![image](https://user-images.githubusercontent.com/45562402/190912642-db22c62d-aa50-464c-87c0-25e5b29bfc77.png)

Might be nice to rework the Release notes to take advantage of this - grouping each minor version with drop downs - but certainly outside the scope here

![image](https://user-images.githubusercontent.com/45562402/190912685-5d6dccaa-eb13-4c59-a326-fbe1c1b3b5ae.png)

Removing this removes some configuration options. Could you try my suggestion above locally? This works for me (e.g. removed the checkbox and added line breaks)

<img width="767" alt="image" src="https://user-images.githubusercontent.com/61934744/190913668-cdc282c0-0a6e-4ff6-85de-7166f4bb7248.png">

Thx @rhshadrach 
Thanks @phofl for the corrections here.
PERF: Improve performance for MultiIndex.isin
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).
- [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.

```
       before           after         ratio
     [85246fe4]       [d6015d67]
     <sym_diff^2>       <isin_performance>
-     3.48±0.01ms       3.13±0.1ms     0.90  multiindex_object.Isin.time_isin('string')
-     3.41±0.02ms      1.46±0.02ms     0.43  multiindex_object.Isin.time_isin('int')
-     10.2±0.04ms      1.54±0.02ms     0.15  multiindex_object.Isin.time_isin('datetime')
```


Labels:
name: Performance
description: Memory or execution speed performance
name: MultiIndex

Comments:
Thanks @phofl
REGR: Loc.setitem with enlargement raises for nested data
State: closed

- [x] closes #48614 (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: Indexing
description: Related to indexing on series/frames, not to indexes themselves
name: Regression
description: Functionality that used to work in a prior pandas version
name: Nested Data
description: Data where the values are collections (lists, sets, dicts, objects, etc.).

Comments:
thx @datapythonista 
@meeseeksdev backport 1.5.x
TST: add test case for PeriodIndex in HDFStore(GH7796)
State: closed

- [x] closes #7796
- [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).

Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: IO HDF5
description: read_hdf, HDFStore

Comments:
Thanks @paradox-lab
BUG: Fix metadata propagation in df.corr and df.cov, GH28283
State: closed

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


Labels:
name: metadata
description: _metadata, .attrs

Comments:
Thanks @yuanx749
WIP: Multichar comment
State: closed

- [x] closes #8727
- [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.
- [ ] 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: 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. Additionally, new features such as this should have associated issued with the core maintainers agreeing that it's worth pursuing. If interested in continuing, please open an associated issue first to gauge interest.
Revised the doc-string for _app_template to bring in line with curren…
State: closed

Revised the doc-string for _app_template to bring in line with current code for aggregate(), in particular regarding the advent of Named Aggregation.

Also fixed text in "See Also" section, where the entries for groupby.transform and aggregate had their text swapped.

- [X] closes #47974



Labels:
name: Docs
name: Apply
description: Apply, Aggregate, Transform, Map

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.
@DRudel - do you have any interest in continuing this? If not, okay if I push it over the finish line?
Sorry for dropping this. Life intervened.
Yes, it would be great if you could take it.
Thanks so much!

On Sun, Nov 13, 2022 at 7:06 AM Richard Shadrach ***@***.***>
wrote:

> @DRudel <https://github.com/DRudel> - do you have any interest in
> continuing this? If not, okay if I push it over the finish line?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/48613#issuecomment-1312752162>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABGGJ7MMXXV2ETE2X7YKKPLWID7WVANCNFSM6AAAAAAQPEQGTI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>


-- 

"A false conclusion, once arrived at and widely accepted is not dislodged
easily, and the less it is understood, the more tenaciously it is held." -
Cantor's Law of Preservation of Ignorance.

Thanks @DRudel and @rhshadrach for finishing this up!
Thanks @DRudel!
Thanks so much for finishing this! Sorry I got tied up.

On Sat, Dec 17, 2022 at 12:26 PM Richard Shadrach ***@***.***>
wrote:

> Thanks @DRudel <https://github.com/DRudel>!
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/48613#issuecomment-1356459041>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABGGJ7NS77H54TQQUFRKANTWNYOZFANCNFSM6AAAAAAQPEQGTI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>


-- 

"A false conclusion, once arrived at and widely accepted is not dislodged
easily, and the less it is understood, the more tenaciously it is held." -
Cantor's Law of Preservation of Ignorance.
TYP: tighten Axis
State: closed

`axis` can only be `Literal[0, 1, "index", "columns"]`. This PR tightens `Axis = Union[int, str]` to `Axis = Union[int, Literal["index", "columns"]]`. A future PR will take care of ints (currently 81 mypy errors).

xref https://github.com/pandas-dev/pandas-stubs/issues/284

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

Comments:
Note: I think `"rows"` is accepted too:

https://github.com/pandas-dev/pandas/blob/bf856a85a3b769821809ff456e288542af16310c/pandas/core/generic.py#L489

But I think it's not publicized well and maybe should be deprecated
> Note: I think `"rows"` is accepted too:

Yes, the following works:

```py
>>> pd.DataFrame({"A": [1, 2, 3]}, index=["A", "B", "C"]).rename({"A": "0"}, axis="rows")
   A
0  1
B  2
C  3
```

> But I think it's not publicized well and maybe should be deprecated

It is definitely not well publicized - but it feels like an intuitive counterpart to `columns`. I will look into adding `"rows"` to `Axis` (from a typing perspective, not documentation) - can easily be removed if we try to deprecate it later.
Thanks @twoertwein