Skip to content
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

PR for #553: Fix potential crasher in _getarguments #554

Merged
merged 2 commits into from Nov 28, 2022
Merged

PR for #553: Fix potential crasher in _getarguments #554

merged 2 commits into from Nov 28, 2022

Conversation

edreamleo
Copy link
Contributor

@edreamleo edreamleo commented Nov 28, 2022

See #553. This PR could be called an emergency fix.

flake8 reported the error. Unit tests did not.

Still unresolved: creating a unit test that should have failed :-) See #545, which suggest better test coverage.

@edreamleo edreamleo mentioned this pull request Nov 28, 2022
4 tasks
@lieryan
Copy link
Member

lieryan commented Nov 28, 2022

Thanks @edreamleo, I've added a test that covers this function now.

@lieryan lieryan self-assigned this Nov 28, 2022
@lieryan lieryan added the bug Unexpected or incorrect user-visible behavior label Nov 28, 2022
@lieryan lieryan added this to the 1.6.0 milestone Nov 28, 2022
@lieryan lieryan merged commit 61c2b05 into python-rope:master Nov 28, 2022
@edreamleo edreamleo deleted the ekr-getarguments branch November 28, 2022 20:03
@edreamleo
Copy link
Contributor Author

@lieryan Thanks for adding the unit test!

BTW, I have just added support in Leo for running flake8 automatically when any file changes. So now I'll be using a work flow more similar to yours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or incorrect user-visible behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants