-
Notifications
You must be signed in to change notification settings - Fork 13
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
improve installing via pip #121
Comments
I nearly forgot: the recommended install of the dependencies is either via the package manager (on linux), as that installs also libdiscid or to use one of the packages mentioned here (also including a libdiscid binary for Windows and Mac): |
The current use of: musicbrainz-isrcsubmit/setup.py Lines 54 to 55 in cb034c6
Does not work. By the time setuptools has parsed this, the previous use of There are three possible solutions:
|
so we don't have to import isrcsubmit. This should enable setup.py to evaluate the dependencies and pip to install the direct dependencies. refs #121
for setup.py and #121 So it looks like we did have an automatic way to write the version in multiple places.
This is basically implemented, but currently not active because I somehow can't deploy to PyPI: |
After also fixing python-discid and testing with
Of course:
I am not going to fix this now, as it would be a bit more complex. Just for reference there is another alternative library, python-libdiscid which is using the same C library libdiscid. It is not using ctypes but is compiled against libdiscid directly. This fails on install:
So it has the advantage to fail early, but it also needs the header files (which python-discid doesn't) and the error message you get might not be "straightforward". |
isrcsubmit needs at least one non-python package (libdiscid, C library), so it can't be installed completely via pip.
However, when installing all python modules you will get a better error message like:
Pip then probably only installs into /usr/local/bin, which might or might not be in the $PATH.
This was probably the purpose of #116, even though was not mentioned in the subject.
The text was updated successfully, but these errors were encountered: