-
Notifications
You must be signed in to change notification settings - Fork 264
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
Issue 68, 67: add additional exception handling to patching code #70
Conversation
One question/issue - this uses a minimal approach to exception handling, but arguably it should do pokemon catching since if anything goes wrong while patching/unpatching it's probably better to keep going rather than bomb out and leave things in an odd state |
I was actually just working on a work project that uses freezegun as a dependency and ran into this. Within a minute of hitting the bug, I checked my email and saw this PR. Sometimes open source is really great. Thanks for your help! |
Just saw your question: I think all of those |
I'm more thinking that the code should be:
rather than being explicit about which exceptions to catch. But agree that it should be |
PS thanks for a nifty tool! |
Oh, I see. I'm always a bit nervous to have blanket (going to fix the Thanks again! |
Issue 68, 67: add additional exception handling to patching code
As soon as I tried the new version with my work project I ran into a RuntimeError so it appears that your suggestion is necessary. Added with 47d113e. Going to do some more testing, but I will release a new version shortly. |
Yes, just ran into exactly same issue on my project! On Monday, 29 December 2014, Steve Pulec notifications@github.com wrote:
Sent from my phone, please excuse any mistakes. |
Adds more exception handling while patching modules to handle various issues that can arise. I think this will fix #68, #67