You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why both of your modules use the same pip install folders? I have server with several running scripts. Some of the scripts use pyzabbix module, and another ones py-zabbix module (scripts from the internet, I don't have time to review every one of them). And one bunch of them is always not working because of using the same name from another module.
I was able to fix it by installing pyzabbix, renaming its folder to pyzabbix2 and uninstalling and then installing py-zabbix and using "from pyzabbix2 import ZabbixAPI" for the first module
But this is fundamentally wrong!
Maybe you should somehow cooperate and use you own names/folders to avoid such conflicts?
The text was updated successfully, but these errors were encountered:
Why both of your modules use the same pip install folders? I have server with several running scripts. Some of the scripts use pyzabbix module, and another ones py-zabbix module (scripts from the internet, I don't have time to review every one of them). And one bunch of them is always not working because of using the same name from another module.
Modules installation paths:
py-zabbix (https://github.com/adubkov/py-zabbix)
/usr/local/lib/python3.8/dist-packages/py_zabbix-1.1.7.dist-info/*
/usr/local/lib/python3.8/dist-packages/pyzabbix/*
/usr/local/lib/python3.8/dist-packages/zabbix/*
pyzabbix (https://github.com/lukecyca/pyzabbix)
/usr/local/lib/python3.8/dist-packages/pyzabbix-1.0.0.dist-info/*
/usr/local/lib/python3.8/dist-packages/pyzabbix/*
I was able to fix it by installing pyzabbix, renaming its folder to pyzabbix2 and uninstalling and then installing py-zabbix and using "from pyzabbix2 import ZabbixAPI" for the first module
But this is fundamentally wrong!
Maybe you should somehow cooperate and use you own names/folders to avoid such conflicts?
The text was updated successfully, but these errors were encountered: