From jorisvandenbossche at gmail.com Tue Dec 5 05:45:56 2023 From: jorisvandenbossche at gmail.com (Joris Van den Bossche) Date: Tue, 5 Dec 2023 11:45:56 +0100 Subject: [Pandas-dev] PDEP-8: In-place methods in pandas (i.e. deprecating the inplace keyword) In-Reply-To: References: Message-ID: Reminder about this discussion: if there are no more comments, we are planning to start a vote in a few days. On Mon, 13 Nov 2023 at 15:53, Joris Van den Bossche < jorisvandenbossche at gmail.com> wrote: > Hi list, > > There is proposal to deprecate and eventually remove the `inplace` keyword > (in most places): PDEP-8 (https://github.com/pandas-dev/pandas/pull/51466). > This has been open for quite a while, and I just updated the text to > reflect the latest state of the discussion, and wanted to bring this up on > the mailing list here as well. > > Feedback goes to the PR: https://github.com/pandas-dev/pandas/pull/51466 > If you want to see a rendered version of the text: > https://jorisvandenbossche.github.io/pandas-website-preview/pdeps/0008-inplace-methods-in-pandas.html > (our website does not yet render them before being merged) > > And posting the abstract here as well. The PDEP proposes: > > - > > The inplace parameter will be removed from any method which can never > update the underlying values of a pandas object inplace or which alters the > shape of the object, and where the inplace=True option is only > syntactic sugar for reassigning the result to the calling DataFrame/Series. > - > > As a consequence, the inplace parameter is only kept for those methods > that can modify the underlying values of a pandas object inplace, such as > fillna or replace. > - > > With the introduction of Copy-on-Write (PDEP-7[1] > ), > users don?t need the inplace keyword to avoid a copy of the data. > - > > For those methods that will keep the inplace=True option: > - > > the method will do an attempt to do the operation inplace but still > silently copy when needed (for Copy-on-Write), i.e. there is no guarantee > it is actually done inplace. > - > > the method will return the calling object (self), instead of the > current None. > > > For the full proposal and motivation, see the links above. > > Feedback welcome! > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From li.thomas3124 at gmail.com Fri Dec 8 17:37:44 2023 From: li.thomas3124 at gmail.com (Thomas Li) Date: Fri, 8 Dec 2023 17:37:44 -0500 Subject: [Pandas-dev] ANN: pandas v2.1.4 Message-ID: We are pleased to announce the release of pandas v2.1.2. This is a patch release in the 2.1.x series and includes some regression fixes and bug fixes. We recommend that all users in the 2.1.x series upgrade to this version. See the release notes for a list of all the changes. The release can be installed from PyPI python -m pip install --upgrade pandas==2.1.4 Or from conda-forge mamba install -c conda-forge pandas==2.1.4 Please report any issues with the release on the pandas issue tracker . Thanks to all the contributors who made this release possible. -------------- next part -------------- An HTML attachment was scrubbed... URL: From li.thomas3124 at gmail.com Fri Dec 22 18:05:33 2023 From: li.thomas3124 at gmail.com (Thomas Li) Date: Fri, 22 Dec 2023 15:05:33 -0800 Subject: [Pandas-dev] ANN: pandas v2.2.0rc0 Message-ID: We are pleased to announce a release candidate for pandas 2.2.0. If all goes well, we'll release pandas 2.2.0 in about two weeks. See the whatsnew( https://pandas.pydata.org/pandas-docs/version/2.2.0rc0/whatsnew/v2.2.0.html) for a list of all the changes. The release will be available on conda-forge and PyPI. The release can be installed from PyPI python -m pip install --upgrade --pre pandas==2.2.0rc0 Or from conda-forge conda install -c conda-forge/label/pandas_rc pandas==2.2.0rc0 Please report any issues with the release candidate on the pandas issue tracker. -------------- next part -------------- An HTML attachment was scrubbed... URL: