-
Notifications
You must be signed in to change notification settings - Fork 163
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
247 is alive completion #283
Conversation
@gwelymernans ^^^ |
I can't explain this, but I found a workaround for this issue which might hint at the reason. I don't really know what's happening, but I found that adding these two lines to the else in else:
mod_name, attr_name = type_name.rsplit('.', 1)
+ if mod_name == 'collections' and attr_name in ('Iterable', 'Iterator'):
+ mod_name = 'collections.abc'
try: I'm not suggesting that as a patch, but it might help give you some idea what's going on. If not... it's a potential ugly workaround. There is probably an underlying issue here that will affect similar cases, though, which should be fixed. Hope it helps... |
OK, so #247 is truly fixed, but now we have another problem with Python 3.8. Let us split this PR into two. The lesson is simple |
https://build.opensuse.org/request/show/764326 by user dimstar_suse - Add isAlive_failed_test.patch as a fix for gh#python-rope/rope#283
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran through all changes and think they are good. Can't say more deep comment in the lack of experience in rope project development.
This is an attempt to fix #247, but still unsuccesful.
@soupytwist , any idea, what's going on? I have tried to replace
threading.Thead.isAlive
(which has been deprecated and unnecessary since 2.6) with.join
(which I guess will never be deprecated), but still doesn’t seem to work. Why rope doesn’t suggest it?