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
Both the API distributed with IDPS and the PyPi package share the package name 'isx'
This can cause ambiguity as to which package is installed when trying to automate package installation and dependency checking using setup tools or another method. Perhaps the API shipped with IDPS should be renamed to isx_api or something similar in future releases.
Cheers!
The text was updated successfully, but these errors were encountered:
Both the API distributed with IDPS and the PyPi package share the package name 'isx'
This can cause ambiguity as to which package is installed when trying to automate package installation and dependency checking using setup tools or another method. Perhaps the API shipped with IDPS should be renamed to isx_api or something similar in future releases.
Cheers!
This is intentional. This way the pure python version can act as a drop in replacement for the IDPS version
That makes sense, but currently there isn't feature parity between the two packages which does cause some trouble when trying to point setuptools to one vs the other on install. Could it make more sense to have one package (or both) have different names and then just import them with an alias as isx? import isx_api as isx and import isx_py as isx or something similar? This then allows automated tools to easily differentiate the two packages, but maintains the future ability to have the pure python version serve as a drop-in replacement.
Both the API distributed with IDPS and the PyPi package share the package name 'isx'
This can cause ambiguity as to which package is installed when trying to automate package installation and dependency checking using setup tools or another method. Perhaps the API shipped with IDPS should be renamed to isx_api or something similar in future releases.
Cheers!
The text was updated successfully, but these errors were encountered: