Skip to content

TagLab load order issue on Windows#212

Open
eth42 wants to merge 1 commit intocnr-isti-vclab:mainfrom
eth42:patch-1
Open

TagLab load order issue on Windows#212
eth42 wants to merge 1 commit intocnr-isti-vclab:mainfrom
eth42:patch-1

Conversation

@eth42
Copy link
Copy Markdown

@eth42 eth42 commented Mar 18, 2026

Hi,

The installation process of TagLab worked just fine on a Win11 setup with msys2 and gnu compiler suite inside a virtualenv, which thankfully allowed to use the pip installs for rasterio and gdal in the absence of msvc tools. However, when starting TagLab, the process quietly dies on the rasterio import in QtAlignmentToolWidget.py. After fiddling around, I noticed that the rasterio import works just fine, when run in REPL or inside a minimal test script. I guess it has something to do with the load order of libraries, though I cannot pinpoint the issue any further. What fixed it for me is to add import rasterio as _rio (unused import) to the top of TagLab.py. My suggestion is to just add that line, to fix any load order issues with rasterio, as it is going to be imported anyhow and doing it earlier does not hurt, does it?

Best
Erik

PS: For some reason, the diff includes addition and deletion of the line sys.exit(app.exec_()). I don't know if that's a bug in the diff, but the result is of course identical.

Added an early import of rasterio in the main script to fix a load order related issue on WIndows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant