Message326182
| Author |
gvanrossum |
| Recipients |
Anders.Hovmöller, gvanrossum, jaraco, ned.deily, ronaldoussoren, tdsmith, vinay.sajip |
| Date |
2018年09月23日.20:59:41 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1537736381.28.0.956365154283.issue22490@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I would love to know how to repro the original bug so I can demonstrate this actually fixes it.
Here's what I think should be the repro:
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 -c 'import subprocess; p = subprocess.Popen([".mypy/venv/bin/python3","-m","mypy.dmypy","-h"]).communicate()'
The setup is that .mypy/venv is a virtualenv that has mypy.dmypy installed. This is what failed for the user who reported this.
Unfortunately this does not fail for me (with a framework build from master installed). Would I have to do the install via brew? (I would have to learn about locally testing modified brew recipes, I suppose.) |
|