Hi guys, thanks for the responses, I missed the bug in the PyICU itself. But my problem can't be solved by debian package. I use virtualenv (and tox) to separate development environment from my system, so the ability to install pyicu using pip is crucial and can't be bypassed by a debian package.
I'll try to bypass it with environment variables, but that's not going to be easy way out. Regards, Vlastimil ne 3. 2. 2019 v 15:18 odesílatel László Böszörményi (GCS) <g...@debian.org> napsal: > Control: tags -1 +wontfix > Control: severity -1 wishlist > > Hi Vlastimil, > > On Wed, Jan 30, 2019 at 1:45 PM Vlastimil Zima <vlastimil.z...@gmail.com> > wrote: > > after upgrading libicu-dev, I can't install PyICU using pip, due to an > error: > > > > FileNotFoundError: [Errno 2] No such file or directory: > 'icu-config': 'icu-config' > > > > I found no replacement of the icu-config, hence I assume the file > disappeared by an accident. > As others pointed out, this is documented at several places. In the > changelog of the package (build without icu-config)[1], ICU upstream > (the icu-config tool has been deprecated)[2] and in a bug report of > PyICU (please use pkg-config to detect icu)[3]. The latter also > reveals its the PyICU developer who don't want to use the new ICU > development location method (pkg-config). > On the other hand, PyICU is packaged and up-to date - you don't have > to install it via pip. But if you do, according to the PyICU > maintainer can use environmental variables to help its installation. > > Regards, > Laszlo/GCS > [1] https://packages.qa.debian.org/i/icu/news/20190124T064926Z.html > [2] http://site.icu-project.org/download/63 > [3] https://github.com/ovalhub/pyicu/issues/92 > [4] https://packages.qa.debian.org/p/pyicu.html >
