Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyPi package name mirrors API package name #51

Open
austin2118ace opened this issue Feb 18, 2024 · 2 comments
Open

PyPi package name mirrors API package name #51

austin2118ace opened this issue Feb 18, 2024 · 2 comments

Comments

@austin2118ace
Copy link

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!

@sg-s
Copy link
Contributor

sg-s commented Feb 19, 2024

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

@austin2118ace
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants