diff options
| author | toofar <toofar@spalge.com> | 2023-10-20 17:30:15 +1300 |
|---|---|---|
| committer | toofar <toofar@spalge.com> | 2023-10-20 17:30:59 +1300 |
| commit | 50e81170991a83999cfe55756199565df0b7a842 (patch) | |
| tree | b986f4e90a287eef181f97c2bfc7ede6f4f8b0d2 | |
| parent | fa862c786e676d64837ec7258e6a30f8c99ac017 (diff) | |
| download | qutebrowser-50e81170991a83999cfe55756199565df0b7a842.tar.gz qutebrowser-50e81170991a83999cfe55756199565df0b7a842.zip | |
fix typo
if -> is
where -> were
| -rw-r--r-- | qutebrowser/utils/qtutils.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/qutebrowser/utils/qtutils.py b/qutebrowser/utils/qtutils.py index 1f5da2dcd..2c103c6b8 100644 --- a/qutebrowser/utils/qtutils.py +++ b/qutebrowser/utils/qtutils.py @@ -89,8 +89,8 @@ def version_check(version: str, With `compiled=False` only the runtime Qt version (1) is checked. You can often run older PyQt versions against newer Qt versions, but you - won't be able to access any APIs that where only added in the newer Qt - version. So if you want to check if a new feature if supported, use the + won't be able to access any APIs that were only added in the newer Qt + version. So if you want to check if a new feature is supported, use the default behavior. If you just want to check the underlying Qt version, pass `compiled=False`. |