Skip to content

Conversation

@ddanier
Copy link
Contributor

I had problems with errors like:
Exception TypeError: "'NoneType' object is not callable" in > ignored

After much digging I found, that os.kill is None in this case while os still exists. No clue how Python managed to get this state, but my change fixes the problem.

@ByronByron added this to the v2.0.6 - Bugfixes milestone Jun 2, 2016
@ByronByron merged commit e0b21f4 into gitpython-developers:masterJun 2, 2016
@Byron
Copy link
Member

Byron commented Jun 2, 2016

Thank you very much ! It's a shame python is so unreliable when the process is on it's way down, and even though I believe they have good reasons for that, just removing standard library functions is certainly a terrible way to communicate these.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ddanier@Byron