-
Notifications
You must be signed in to change notification settings - Fork 243
Closed
Labels
maintenanceBoring but important stuff for the core devsBoring but important stuff for the core devsupstreamBug or missing feature of upstream core GMTBug or missing feature of upstream core GMT
Milestone
Description
I build the GMT master branch from source code and install it to /home/user/opt/GMT-master/. It's the only GMT version installed on my computer.
Here is the output of pygmt.show_versions()
>>> import pygmt
>>> pygmt.show_versions()
PyGMT information:
version: v0.6.1.dev3+g26d72c896
System information:
python: 3.9.7 (default, Sep 16 2021, 13:09:58) [GCC 7.5.0]
executable: /home/user/opt/miniconda/bin/python
machine: Linux-5.15.18-200.fc35.x86_64-x86_64-with-glibc2.34
Dependency information:
numpy: 1.22.3
pandas: 1.4.1
xarray: 2022.3.0
netCDF4: 1.5.8
packaging: 21.3
ghostscript: 9.55.0
gmt: 6.4.0_434ed18_2022.03.11
GMT library information:
binary dir: /home/user/opt/miniconda/bin
cores: 80
grid layout: rows
image layout:
library path: /home/user/opt/GMT-master/lib64/libgmt.so
padding: 2
plugin dir: /home/user/opt/GMT-master/lib64/gmt/plugins
share dir: /home/user/opt/GMT-master/share
version: 6.4.0
There are some issues here:
- It should also report the version information of optional dependencies (i.e., geopandas) if available
- The GMT version information
gmt: 6.4.0_434ed18_2022.03.11is obtained by callinggmt --version. However, when multiple GMT versions are installed, the commandgmtand the librarylibgmtmay come from different GMT verisons. For example, if I have GMT 6.3 in my conda environment and GMT dev in another installation path, PyGMT may load the GMT 6.3 library but find GMT dev comman, or vice versa, depending on the settings of PATH and GMT_LIBRARY_PATH. It causes some confusion because PyGMT reports inconsistent GMT versions. I think we should remove thegmt: 6.4.0_434ed18_2022.03.11information. - The GMT's
binary dir: /home/user/opt/miniconda/bininformation comes from GMT'sAPI_BINDIRparameter in libgmt. It's the path of the program that loads and call the libgmt library. So, for GMT CLI, it points to GMT's bin directory, but for PyGMT, it's the path of the python interpreter. So the information is useless and also cause some confusion. I think we should remove it too.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
maintenanceBoring but important stuff for the core devsBoring but important stuff for the core devsupstreamBug or missing feature of upstream core GMTBug or missing feature of upstream core GMT