This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Anders.Hovmöller, gvanrossum, jaraco, ned.deily, ronaldoussoren, tdsmith, vinay.sajip
Date 2018-09-24.05:07:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I had the some problem when using mypy. What does reproduce the issue is the following:

* Create *two* venv environments
* Install mypy in one of them
* Activate the other
* Run the subprocess call in the activated venv

I then get a message about not being able to find mypy:

.../some-env/bin/python3: No module named mypy.dmypy

I don't get the message when I call subprocess outside of a venv.

I haven't checked yet if my patch fixes this issue, that will have to wait for later this week.
Date User Action Args
2018-09-24 05:07:00ronaldoussorensetrecipients: + ronaldoussoren, gvanrossum, vinay.sajip, jaraco, ned.deily, Anders.Hovmöller, tdsmith
2018-09-24 05:07:00ronaldoussorensetmessageid: <>
2018-09-24 05:07:00ronaldoussorenlinkissue22490 messages
2018-09-24 05:07:00ronaldoussorencreate