Bug#958114: can not use because commonutil can not be imported

2020-05-03 Thread Christian Kastner
On 2020-05-02 14:23, Tiziano Zito wrote: > Thanks for reporting the issue. Should I open a sister-issue on libsvm > upstream GitHub repo? > https://github.com/cjlin1/libsvm/issues Oh, I honestly forgot about that. Yes, a sister issue would be good. I'll take care of it, but thanks for the offer

Bug#958114: can not use because commonutil can not be imported

2020-05-02 Thread Tiziano Zito
Hi Christian, I eventually filed an issue with the PyPI maintainer on GitHub [1] with a request for them to resolve this with upstream directly, as that seemed to be the most appropriate course of action. Thanks for reporting the issue. Should I open a sister-issue on libsvm upstream GitHub

Bug#958114: can not use because commonutil can not be imported

2020-05-02 Thread Christian Kastner
Hi Tiziano, On 2020-04-24 12:37, Tiziano Zito wrote: >> In any case, the official version has certainly seen far more widespread >> use than the PyPI version (the former being around for a decade, the >> latter for a few months), so we need to be aware that changing this >> might break a lot of

Bug#958114: can not use because commonutil can not be imported

2020-04-29 Thread Christian Kastner
On 2020-04-24 12:37, Tiziano Zito wrote: >> In any case, the official version has certainly seen far more widespread >> use than the PyPI version (the former being around for a decade, the >> latter for a few months), so we need to be aware that changing this >> might break a lot of existing code

Bug#958114: can not use because commonutil can not be imported

2020-04-24 Thread Tiziano Zito
On Fri 24 Apr, 12:24 +0200, Christian Kastner wrote: I have to disagree on that. I'd agree if PyPI were hosting the official version, but this appears to be provided by a third party. This unofficial version already conflicts with upstream, so future conflicts and issues cannot be ruled out.

Bug#958114: can not use because commonutil can not be imported

2020-04-24 Thread Tiziano Zito
On Thu 23 Apr, 22:46 +0200, Christian Kastner wrote: Upstream is actually creating a libsvm namespace. When installing libsvm using pip, the package layout is the following: libsvm ├── __init__.py ├── commonutil.py ├── svm.py └── svmutil.py While that would solve the namespace problem, it

Processed: Re: Bug#958114: can not use because commonutil can not be imported

2020-04-23 Thread Debian Bug Tracking System
Processing control commands: > clone 958114 -1 -2 Bug #958114 [python3-libsvm] can not use because commonutil can not be imported Bug 958114 cloned as bugs 958640-958641 > reassign -2 python3-liblinear Bug #958641 [python3-libsvm] can not use because commonutil can not be imported Bug reas

Bug#958114: can not use because commonutil can not be imported

2020-04-23 Thread Christian Kastner
Control: clone 958114 -1 -2 Control: reassign -2 python3-liblinear On 2020-04-18 18:16, Tiziano Zito wrote: > The libsvm package has changed interface and can not be used anymore. With > the > python3-libsvm package from sid the following happens: > > python3 -c 'import svmutil' > Traceback

Bug#958114: can not use because commonutil can not be imported

2020-04-18 Thread Tiziano Zito
Package: python3-libsvm Version: 3.24+ds-3 Severity: important Hi! The libsvm package has changed interface and can not be used anymore. With the python3-libsvm package from sid the following happens: python3 -c 'import svmutil' Traceback (most recent call last): File "", line 1, in File