cannot install from pip about pydsstools HOT 9 CLOSED

You are supposedly using a Python 3.10 environment in Conda; however, the compiler indicates you are using Python 3.9, which is likely the system Python. I recommend using the system or non-Conda Python through a virtual environment (using venv, virtualenv, etc.) for compiling pydsstools to avoid accidentally messing up the system Python and potentially breaking the OS. As I mentioned earlier, you may need to install the python3-dev and additional development packages via apt install package_name.

from pydsstools.

I'll chime in to reference #45 which was the last time I attempted (successfully) to install pydsstools in a Linux environment. The main problem I had at the time was that USACE's heclib binary (a dependency for pydsstools) was corrupted, so I needed to download and point to an alternate version of that binary. As mentioned in the issue, since then I have stayed on an old commit of pydsstools. It could be that things are smoother now, but I didn't want to take the risk of updating to the latest due to this: #43 which references a function rename here: HydrologicEngineeringCenter/hec-dss#165.

I don't want to dissuade you from trying the latest, I just wanted to give a complete answer since this is pretty nuanced. If you want a method that 100% works, see my issue #45 which calls out a specific commit to use, and specific heclib binary to use.

from pydsstools.

@12rambau The compiler can't find the Python header file, which is unrelated to this library. Ensure your conda environment has access to the header files and static libraries of Python. You may need to install python3-dev or the equivalent for your Linux installation.

from pydsstools.

I did several time, the machine is a bit weird I think you are searching for the exact Python header that you would expect on a classic Linux machine but for exotic machine like mine it doesn't work. Where do you expect Python.h to be ?

from pydsstools.

@12rambau you can probably ignore my earlier comment since as @gyanz pointed out, the problem is at the highest level (the environment) rather than among some dependency chain specific to this library. Conda makes things hard.

from pydsstools.

I'm on purpose installing version 3.9 to matchthe databricks environment of my company. It's too error pronefor us to rely on a setup.py file that compiles a lib upon installation. Isn't it possible from your side to compile it when you make a new release of the lib ?
The same way GDAL is compiled by rasterio for example ? This way you always controls what is installed with the python package and 100% sure things are actually compatible.

from pydsstools.

Binary wheels can't be made available for Linux via pip due to the guidelines outlined in PEP 513.

from pydsstools.

ok then I'll stop bother you, my company machine have a very exotic setup (that I'm complaining about to the IT services since day 1) that prevent any installation that is not a python wheel to run smoothly.

Since I started Conda have been a life saver has it supports compilation of other tools but if you don't want to support it, I will not be able to proceed.

Feel free to close my issue if it's a won't fix and/or ping me if you need a beta tester for a potential conda release.

from pydsstools.

It is not up to me to support or not support wheels for Linux; PyPi/pip do not support Linux wheels. For this reason, I am closing this issue.

from pydsstools.