ENH: move an exception and add a prehook to check for exception place… by dataxerik · Pull Request #48088 · pandas-dev/pandas (original) (raw)

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation27 Commits13 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

dataxerik

This is a follow up from my last MR: #47901. I'm new to prehooks, so I may have went in the wrong direction for the prehook. But, I was thinking of checking the files for class that inherit Exceptions and flagging them. Let me know if another approach is preferred.

I also noticed some other exceptions while working on this.

mroeschke

mroeschke

mroeschke

mroeschke

mroeschke

@dataxerik

@dataxerik

mroeschke

@dataxerik

@dataxerik

@mroeschke

Looked pretty good. Could you fix the merge conflict and see if the Ci failures are related?

@dataxerik

@dataxerik

Looked pretty good. Could you fix the merge conflict and see if the Ci failures are related?

Sounds good. I've merged main

@dataxerik

mroeschke

@mroeschke

Awesome work on this @dataxerik! This will really help make sure users are able to publicly access Warnings and Exceptions in the future!

@jorisvandenbossche

(just getting here from the notification that the issue was closed, so sorry for the late comment)

I think that InvalidComparison is only used internally to raise certain cases which is then catched internally again to do something else or raise a public error. Assuming that's the case, we don't need to expose this exception class publicly?

(the same might be true for LossySetitemError, didn't check in detail, cc @jbrockmendel)

@mroeschke

That's a fair point.

Maybe we can clearly document the exceptions or warnings that are supposed to be internal? My concern is that overtime the "internal" exceptions or warnings may unintentionally become publicly thrown, and at least users could still catch them through pandas.errors

@jbrockmendel

I think that InvalidComparison is only used internally to raise certain cases which is then catched internally again to do something else or raise a public error. Assuming that's the case, we don't need to expose this exception class publicly?

correct. It should always be caught and re-raised. Could clarify that in the docstring.

Ditto for LossySetitemError.

phofl pushed a commit to phofl/pandas that referenced this pull request

Sep 22, 2022

@dataxerik @phofl

pandas-dev#48088)

mroeschke added a commit that referenced this pull request

Sep 26, 2022

…8662)

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

scorecard-action does not have a major version tag.

Temporarily disabling github.repository check to ensure action now works.

https://pandas.pydata.org/docs/reference/api/pandas.merge.html It should be "str | bool" instead of just string

fixed type hint in merge.py

Update indicator type hint in _MergeOperation

Added type hint _MergeOperation init

DOC: Document default value for options.display.max_cols

display.max_cols has a default value of 20 when not running in a terminal such as Jupyter Notebook

Co-Authored-By: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com Co-authored-by: Ralf Gommers ralf.gommers@gmail.com Co-authored-by: Marc Garcia garcia.marc@gmail.com Co-authored-by: Luke Manley lukemanley@gmail.com Co-authored-by: Siddhartha Gandhi siddhartha.a.gandhi@gmail.com Co-authored-by: Torsten Wörtwein twoertwein@users.noreply.github.com Co-authored-by: Xiao Yuan yuanx749@gmail.com Co-authored-by: paradox-lab 57354735+paradox-lab@users.noreply.github.com Co-authored-by: Pedro Nacht 15221358+pnacht@users.noreply.github.com Co-authored-by: dataxerik dsshar@gmail.com Co-authored-by: jbrockmendel jbrockmendel@gmail.com Co-authored-by: Pablo 48098178+PabloRuizCuevas@users.noreply.github.com Co-authored-by: tmoschou 5567550+tmoschou@users.noreply.github.com Co-authored-by: Thomas Li 47963215+lithomas1@users.noreply.github.com Co-authored-by: Richard Shadrach 45562402+rhshadrach@users.noreply.github.com

noatamir pushed a commit to noatamir/pandas that referenced this pull request

Nov 9, 2022

@dataxerik @noatamir

pandas-dev#48088)

noatamir pushed a commit to noatamir/pandas that referenced this pull request

Nov 9, 2022

…ndas-dev#48662)

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

scorecard-action does not have a major version tag.

Temporarily disabling github.repository check to ensure action now works.

https://pandas.pydata.org/docs/reference/api/pandas.merge.html It should be "str | bool" instead of just string

fixed type hint in merge.py

Update indicator type hint in _MergeOperation

Added type hint _MergeOperation init

DOC: Document default value for options.display.max_cols

display.max_cols has a default value of 20 when not running in a terminal such as Jupyter Notebook

Co-Authored-By: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com

Co-authored-by: Matthew Roeschke 10647082+mroeschke@users.noreply.github.com Co-authored-by: Ralf Gommers ralf.gommers@gmail.com Co-authored-by: Marc Garcia garcia.marc@gmail.com Co-authored-by: Luke Manley lukemanley@gmail.com Co-authored-by: Siddhartha Gandhi siddhartha.a.gandhi@gmail.com Co-authored-by: Torsten Wörtwein twoertwein@users.noreply.github.com Co-authored-by: Xiao Yuan yuanx749@gmail.com Co-authored-by: paradox-lab 57354735+paradox-lab@users.noreply.github.com Co-authored-by: Pedro Nacht 15221358+pnacht@users.noreply.github.com Co-authored-by: dataxerik dsshar@gmail.com Co-authored-by: jbrockmendel jbrockmendel@gmail.com Co-authored-by: Pablo 48098178+PabloRuizCuevas@users.noreply.github.com Co-authored-by: tmoschou 5567550+tmoschou@users.noreply.github.com Co-authored-by: Thomas Li 47963215+lithomas1@users.noreply.github.com Co-authored-by: Richard Shadrach 45562402+rhshadrach@users.noreply.github.com