Renaming pylibtiff to libtiff causes issues for some build systems

[jakirkham]

As some build systems (e.g. conda and Linux package managers) can install libtiff when referring to the actual library. Renaming of this package from libtiff to pylibtiff can cause them some confusion. Would it be too much to ask that the package be renamed to pylibtiff?

[djhoese]

I agree with @jakirkham on this. I have a project that depends on this library and installing pylibtiff has become difficult for users that use conda (including me). It has to be installed from pip and can't be put on conda-forge because there is already the C library libtiff. This causes issues where a setup.py can list dependencies that conflict with the conda packages already installed. There is a similar issue with pyhdf/python-hdf4 right now that I'm trying to help resolve.

[pearu]

Sounds reasonable. So, the pylibtiff can be redistributed under the name pylibtiff but the Python package name should remain libtiff.

[djhoese]

If that can be done then that may be best. So it would show up on PyPI as pylibtiff and on conda as pylibtiff, but would be imported as libtiff, right?

[pearu]

yes, that what also I meant.

[pearu]

Resolved by RP #93 .

[nunocalaim]

conda install pylibtiff fails, but conda install libtiff works. did this project got renamed again?

[djhoese]

libtiff is the C library, pylibtiff should still exist on conda-forge:

https://github.com/conda-forge/pylibtiff-feedstock