On Tue, 1 May 2018 at 19:15, Paul Moore wrote:
> Maybe you need --system-site-packages?
DO NOT use this option. The entire point of a virtualenv is to be separate
from both other environments and the system Python site-packages.
The correct way to handle this is to install the modules using the
On Tue, 1 May 2018, Dennis Lee Bieber wrote:
Did you miss:
Dennis,
Yes, I did.
Mea culpa,
Rich
--
https://mail.python.org/mailman/listinfo/python-list
On Tue, 1 May 2018, Paul Moore wrote:
Maybe you need --system-site-packages?
Paul,
Thank you. I changed pyvenv.cfg to 'include-system-site-packages = true'.
Regards,
Rich
--
https://mail.python.org/mailman/listinfo/python-list
On 1 May 2018 at 17:06, Rich Shepard wrote:
> Activating venv and trying to run the project Python tells me it cannot
> find the wxPython4 modules:
>
> Traceback (most recent call last):
> File "./openEDMS.py", line 12, in
> import wx
> ModuleNotFoundError: No module named 'wx'
>
> I've
Activating venv and trying to run the project Python tells me it cannot
find the wxPython4 modules:
Traceback (most recent call last):
File "./openEDMS.py", line 12, in
import wx
ModuleNotFoundError: No module named 'wx'
I've read the Python3 venv standard library doc page (section 28
