Re: No way to import pycurl

 NM> Ok, the problem is that Mystic don't remove/delete completely python2
 NM> field whe I leave it blank then python2 is not "deactivated" so when i
 NM> call a pyhton3 script mystic give me the execution exception error as a
 NM> reported on Mystic wiki using both version of python.

 NM> To tempoaly solve this issue i can give a wrong python2 lib path (like
 NM> "." or something like that) although a warning appear (Cannot initialize
 NM> Python, press a key) before execute pyhton3 script; but this way at

Nothing is ever deactivated in Python when a field is blank.  When its blank 
its looking in all known installation locations for all known versions of 
Python.  This is discussed on the Wiki here: 
http://wiki.mysticbbs.com/doku.php?id=python_install

When you are setting the Python 2 library name to "." you are forcing Mystic to 
not detect Python 2. The fact that it finds something when blank means you 
probably have multiple installations of Python, which as noted on the Wiki is 
going to end in an Access Violation.  Even if you trick Mystic into not finding 
the base Python 2 library itself, the symbols of the modules and system 
libraries will still be found later, and it will cause conflict which results 
in an Access Violation.

So how do we fix it?  Well I may not know but I'll try.

I think first lets see what is on your system.  Please try to run one or both 
of these commands to locate where you have libpython and let me know:

ldconfig -p | grep libpython
sudo find / -name 'libpython*'

... A Skydiver is taken by the gravity of his situation.