Closed pjhartzell closed 4 years ago
hmm, I wonder if the install paths for the DLLs is different per-python version.
Not 100% sure what you're getting at, but the install is using Python 3.8.3. I can experiment with different Python versions if you think there is something there.
https://github.com/hobu/python-pdal-feedstock/blob/master/recipe/scripts/activate.bat is how this gets set. The issue is %PREFIX%\Lib\site-packages\bin
might no longer be the place where pip is installing the plugin DLLs
The plugins are installed at the location specified in the bat file (%CONDA_PREFIX%\lib\site-packages\bin) on my machine.
(python-pdal-test3) PS C:\dev\python\lidar-error-prop\error-prop> $env:CONDA_PREFIX
C:\Users\prest\Miniconda3\envs\python-pdal-test3
(python-pdal-test3) PS C:\dev\python\lidar-error-prop\error-prop> $env:PDAL_DRIVER_PATH
C:\Users\prest\Miniconda3\envs\python-pdal-test\lib\site-packages\bin
But PDAL_DRIVER_PATH is not being set during the install. After unsetting my manually set PDAL_DRIVER_PATH and then installing python-pdal
into a fresh Conda environment, the PDAL_DRIVER_PATH environment variable does not exist (was not created):
(python-pdal-test3) PS C:\dev\python\lidar-error-prop\error-prop> $env:PDAL_DRIVER_PATH
(python-pdal-test3) PS C:\dev\python\lidar-error-prop\error-prop> conda env config vars list
(python-pdal-test3) PS C:\dev\python\lidar-error-prop\error-prop> cd "C:\Users\prest\Miniconda3\envs\python-pdal-test\lib\site-packages\bin"
(python-pdal-test3) PS C:\Users\prest\Miniconda3\envs\python-pdal-test\lib\site-packages\bin> ls
Directory: C:\Users\prest\Miniconda3\envs\python-pdal-test\lib\site-packages\bin
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 4/17/2020 6:51 AM 388608 libpdal_plugin_filter_python.dll
-a---- 4/17/2020 6:51 AM 321024 libpdal_plugin_reader_numpy.dll
(python-pdal-test3) PS C:\Users\prest\Miniconda3\envs\python-pdal-test\lib\site-packages\bin>
Per our brief discussion on jitsi, if I use the standard command prompt rather than powershell, it works fine. Both filters.python and readers.numpy are available in the pdal --drivers
listing and PDAL_DRIVER_PATH is set correctly.
(lidar-error) C:\dev\python\lidar-error-prop\error-prop>echo %CONDA_PREFIX%
C:\Users\prest\Miniconda3\envs\lidar-error
(lidar-error) C:\dev\python\lidar-error-prop\error-prop>echo %PDAL_DRIVER_PATH%
C:\Users\prest\Miniconda3\envs\lidar-error\Library\bin;C:\Users\prest\Miniconda3\envs\lidar-error\lib\site-packages\bin
Per our brief discussion on jitsi, if I use the standard command prompt rather than powershell, it works fine.
Ok, we need to add activate.ps and deactivate.ps scripts to the pdal-python-feedstock.
Addressed in https://github.com/conda-forge/pdal-feedstock/pull/112 Reopen there if there are any future issues with it once the packages are pushed out.
Describe the bug filters.python and readers.numpy are not available when installing python-pdal via Conda into a fresh Conda environment on a Windows machine.
conda create -n python-pdal-test
conda activate python-pdal-test
conda install -c conda-forge python-pdal
pdal --drivers
Expected behavior filters.python and readers.numpy would be available without having to manually set the PDAL_DRIVER_PATH environment variable. In my case,
conda env config vars set PDAL_DRIVER_PATH="C:\Users\prest\Miniconda3\envs\python-pdal-test\Lib\site-packages\bin"
fixed the issue. But this is not user friendly.System/installation information:
pdal --version
$Properties = 'Caption', 'CSName', 'Version', 'BuildType', 'OSArchitecture'
Get-CimInstance Win32_OperatingSystem | Select-Object $Properties | Format-Table -AutoSize