Skip to content

Conversation

@neutrinoceros
Copy link
Contributor

This is an attempt to fix #153
This is my very first experience with ast and I'll admit I don't really know what I'm doing. I added a test based on the issue's description, checked that it failed with the current state of the code base as reported, and applied a minimal patch to make it pass without breaking any other test.

@neutrinoceros neutrinoceros force-pushed the hotfix_issue153 branch 2 times, most recently from 455147d to 856adfb Compare March 5, 2021 17:29
Copy link
Collaborator

@cooperlees cooperlees left a comment

Choose a reason for hiding this comment

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

Thanks! LGTM, This handles the condition and stops us crashing. I can't see a better way to do this. If anyone else can we can forward fix!

@cooperlees cooperlees merged commit 8d8d37b into PyCQA:master Mar 8, 2021
@neutrinoceros neutrinoceros deleted the hotfix_issue153 branch March 8, 2021 17:57
@neutrinoceros
Copy link
Contributor Author

neutrinoceros commented Mar 8, 2021

Thank you for merging !
When do you think I can realistically expect this fix to be released (no rush, just curious) ?
edit: wow it was released before I even asked. Thanks !

@cooperlees
Copy link
Collaborator

Yeah, I have it all automated apart from changes in README.rst - So releasing is easy here. Just need to not let it sit so long so we ship more with less change.

This was referenced Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

crash on tuple expansion in try/except block

2 participants