Closed LingEarth closed 3 years ago
Indeed, the user shouldn't be getting stack traces! I'll take a look...
Oh, the stack trace only happened when I ran with -d to see exactly what was going wrong. Without that, it just crashes with no explanation.
This is fixed in commit ee277f471caf0b31ce522fd58d7ff91481438549 and will be included in the next release.
If I run lexurgy with the --compare-versions flag before I have run it to create the _ev.wli file, it crashes. Running with -d gives the following error:
It would be better to simply display an error about the file not existing, or even just print a warning and then go on to run the sound changes without writing a comparison file.