Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Make sure os is not even partly destroyed#460

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

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 thev2.0.6 - Bugfixes milestoneJun 2, 2016
@ByronByron merged commite0b21f4 intogitpython-developers:masterJun 2, 2016
@Byron
Copy link
Member

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
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
@ddanier@Byron

[8]ページ先頭

©2009-2025 Movatter.jp