Skip to content

Avoid raising bare Exception #1168

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 and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

zaicruvoir1rominet
Copy link
Contributor

@zaicruvoir1rominet zaicruvoir1rominet commented Jul 4, 2024

Summary

Before tackling issue #457, there are some bare Exceptions thrown from within the code.

Here is the logic for changes in Exceptions:

  • use ValueError when issue caused by user input
  • use CSTValidationError & TypeError when issue occurs during the CST validation process
  • use ParserSyntaxError when issue occurs during the parsing process
  • use CSTLogicError to replace all Exception which contained "Logic error" in the cause message
  • remove Exception catch+re-raise when not needed

I'm all for changes if some Exceptions changes are not OK,
In particular, there are some ParserSyntaxError which may not be meaningful - with raw_line=0, raw_column=0 params

Test Plan

Keep the current test plan.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 4, 2024
Copy link

codecov bot commented Jul 4, 2024

Codecov Report

Attention: Patch coverage is 25.49020% with 114 lines in your changes missing coverage. Please review.

Project coverage is 91.29%. Comparing base (8b97600) to head (eb3f2a6).
Report is 9 commits behind head on main.

Files Patch % Lines
libcst/matchers/_matcher_base.py 9.52% 19 Missing ⚠️
libcst/_parser/conversions/expression.py 18.18% 9 Missing ⚠️
libcst/_parser/conversions/statement.py 18.18% 9 Missing ⚠️
...bcst/codemod/commands/convert_format_to_fstring.py 20.00% 8 Missing ⚠️
libcst/_parser/parso/python/tokenize.py 12.50% 7 Missing ⚠️
libcst/_parser/conversions/params.py 14.28% 6 Missing ⚠️
libcst/codegen/gen_matcher_classes.py 16.66% 5 Missing ⚠️
libcst/helpers/_template.py 0.00% 5 Missing ⚠️
libcst/_nodes/base.py 20.00% 4 Missing ⚠️
libcst/_parser/grammar.py 0.00% 4 Missing ⚠️
... and 19 more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1168      +/-   ##
==========================================
+ Coverage   91.26%   91.29%   +0.03%     
==========================================
  Files         261      262       +1     
  Lines       26877    26899      +22     
==========================================
+ Hits        24529    24558      +29     
+ Misses       2348     2341       -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@kiri11
Copy link
Contributor

kiri11 commented Jul 27, 2024

This seems like an improvement, thank you. It's really hard to catch a specific Exception, I have to rely on its message. I hope this gets merged.

Copy link
Member

@zsol zsol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this! I've got a few minor comments but overall looks great!

@zaicruvoir1rominet
Copy link
Contributor Author

Thanks for the support @kiri11 !
You also made me realize some users were perhaps using exception messages in order to manage errors, so I kept all original Exception messages in order to avoid breaking changes.

I hope everything is now ready (apart from that CSTLogicError file location & docstring)

@kiri11
Copy link
Contributor

kiri11 commented Aug 12, 2024

You're welcome! (although I didn't do anything)
Keeping the exception messages backwards-compatible is a great idea, thank you!

zaicruvoir1rominet added 4 commits April 10, 2025 23:35
…belong, to its own file in _parser/_parsing_check.py

* Group all exceptions in _exceptions.py
* Remove now empty file _excep.py (now redundant with _exceptions.py)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants