[BUGFIX] three lines where a print was used without the "f'" - #290
Conversation
Three error messages in split_filtered_country_files_to_tiles were
missing the f-prefix, so {country} was printed literally instead of
the actual country name.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
4b2f9c2 to
0c1488b
Compare
Branch updated — slash normalization removed, f-string fixes keptThanks for the PR! After reviewing it against the changes that landed since it was opened, I've updated the branch so only the relevant fix remains. What was removed and whyThe slash normalization changes (
Since both sides of every comparison and every file path are already slash-free, the extra What was keptThe three missing # before (broken — prints literal "{country}")
cmd, '! Error in osmconvert with country: {country}. Win/out_file_names')
cmd, '! Error in Osmium with country: {country}. macOS/out_file')
cmd, '! Error in Osmium with country: {country}. macOS/out_file_names')
# after (correct)
cmd, f'! Error in osmconvert with country: {country}. Win/out_file_names')
cmd, f'! Error in Osmium with country: {country}. macOS/out_file')
cmd, f'! Error in Osmium with country: {country}. macOS/out_file_names')These three fixes are now the only change on the branch. |
And fixed three lines where a print was used without the "f'"
When trying to generate a map file for a US/ region the program would crash on Windows (and as it turned out later also on WSL) because of the "/" in the regions name.
Pull Request Checklist