hi Xavier, > Pyclewn (and therefore the python program it is debugging with pdb) > runs with the python instance that it has been installed with. Check > the first line of the pyclewn script which may say for example: > > #!/usr/local/bin/python3 > > This is why pyclewn is not seeing the packages of your virtualenv, > hence the import error.
Maybe you can use the "env trick"? Like #!/usr/bin/env python I have not tested it but could work > I don't know venv, but it is likely that venv provides a way to run > pyclewn in your virtualenv. Otherwise you can still change sys.path > before the imports, to fit your virtualenv, or install pyclewn inside > your virtualenv. I haven't yet had the time to try, but thanks for the hints -- pyclewn looks very promising thanks! bye, Marco ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
