Link to issue number:

Follow up from #12753

Summary of the issue:

During debugging for PR #12753 some issues in code around setting language in core.main become evident. In particular:

• wx.Locale object was called locale effectively shadowing built-in Python module. While normally there is no reason to have locale imported in that scope if it is necessary for debugging the name is rather unfortunate.
• except around importing languageHandler and setting language was too broad hiding eventual issues.

Description of how this pull request fixes the issue:

• locale was renamed to wxLocaleObj.
• We're no longer catching any exceptions when importing languageHandler and setting language - if any of these fails NVDA is non functional and the exception should propagate.

Testing strategy:

Ensured that NVDA still starts. Existing unit tests making sure that languageHandler is importable and that the process of setting language does not raise any exceptions.

Known issues with pull request:

None known

Change log entries:

None needed.

Code Review Checklist:

• Pull Request description is up to date.
• Unit tests.
• System (end to end) tests.
• Manual testing.
• API is compatible with existing addons.
• User Documentation.
• Change log entry.
• Context sensitive help for GUI changes.
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers