-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Jishaku version occasionally appears as vNone in selftest #205
Comments
I've encountered this a few times around the place, and last I checked, it traces back to module lookup creation in distutils. If with pip you somehow break one of your packages - or one ends up in a transient state while distutils is trying to deal with it, the creation will fail and distutils will remain forever unable to pull information from any package until the interpreter is restarted. It's not an easy bug to reproduce, and its root cause is not possible to fix because it is caused by pip not us. But, some kind of workaround should be implemented that maybe doesn't rely on distutils if it coughs up evidence that it broke its database. |
なにか必要な情報ありますか? |
jishakuのバージョン情報を取得するには二つの方法があります: 逆に早速で直したいのであれば、 |
Okay, I'll do after I finish exam. |
pkg_resources usage was replaced in #213. I'm going to assume that this fixes this issue. If it occurs again just reopen. |
Summary
When I run
jsk
root command, jishaku show me like this image.Reproduction steps
When I run jsk command.
Checklist
System information
The text was updated successfully, but these errors were encountered: