Commit Graph

18561 Commits

Author SHA1 Message Date
Florian Bruhin 692f8241ca pylint: Add trailing commas to config 2019-10-01 12:38:53 +02:00
Florian Bruhin 24eaecdd09 pylint: Enable overlapping_exceptions
It was moved to a pylint extension because it makes no sense for polyglot
Python 2/3 code, but we're not doing that.
2019-10-01 12:38:30 +02:00
Florian Bruhin c9386b753a pylint: Enable broad_try_clause 2019-10-01 12:37:58 +02:00
Florian Bruhin 8cd65dcc1b pylint: Enable emptystring extension 2019-10-01 12:35:55 +02:00
Florian Bruhin 5dd784fcfc pylint: Skip bad-builtin extension 2019-10-01 12:26:06 +02:00
Florian Bruhin 2fa32246c7 pylint: Ignore DummyBox errors
pylint complains because msgbox.msgbox() can return DummyBox, but we know
that's not the case in tests/unit/misc/test_msgbox.py.
2019-10-01 12:20:17 +02:00
Florian Bruhin fb6d95f90c Remove pointless assignments 2019-10-01 12:16:37 +02:00
Florian Bruhin 4ff40fb746 pylint: Disable no-else-continue 2019-10-01 12:14:34 +02:00
Florian Bruhin f35ff2d70e Clarify Python version comments 2019-10-01 12:12:30 +02:00
Florian Bruhin feb06c3e9f pylint: Remove protected-access ignores in special methods 2019-10-01 12:12:17 +02:00
Florian Bruhin 59f5d00ce7 pylint: Ignore import-outside-toplevel
There are good reasons to do those.
2019-10-01 12:07:22 +02:00
Florian Bruhin 7e91ce94cf Remove unused-import pylint disables for typing
This should work fine for the newest pylint/astroid versions.
2019-10-01 12:03:58 +02:00
Florian Bruhin 3523bac245 Remove old segfault_test script 2019-10-01 11:54:40 +02:00
Florian Bruhin 21e9b9b41f Specify 'check' with subprocess.run 2019-10-01 11:54:18 +02:00
pyup-bot 2dfe2b170a Update soupsieve from 1.9.3 to 1.9.4 2019-09-30 21:08:21 +02:00
pyup-bot 6fdd0a4b69 Update pytest-mock from 1.10.4 to 1.11.0 2019-09-30 21:08:20 +02:00
pyup-bot c1013dd722 Update pytest from 5.1.3 to 5.2.0 2019-09-30 21:08:19 +02:00
pyup-bot 0f492125d1 Update hypothesis from 4.36.2 to 4.37.0 2019-09-30 21:08:18 +02:00
pyup-bot c5c2315159 Update cheroot from 6.5.8 to 7.0.0 2019-09-30 21:08:17 +02:00
pyup-bot bee1301699 Update pylint from 2.3.1 to 2.4.2 2019-09-30 21:08:16 +02:00
pyup-bot a88606ffa2 Update astroid from 2.2.5 to 2.3.1 2019-09-30 21:08:15 +02:00
pyup-bot 6ae2608a42 Update flake8-docstrings from 1.4.0 to 1.5.0 2019-09-30 21:08:14 +02:00
pyup-bot 6ca15d582c Update urllib3 from 1.25.5 to 1.25.6 2019-09-30 21:08:12 +02:00
pyup-bot badf2f3dfb Update urllib3 from 1.25.5 to 1.25.6 2019-09-30 21:08:11 +02:00
pyup-bot b25017dcab Update urllib3 from 1.25.5 to 1.25.6 2019-09-30 21:08:10 +02:00
pyup-bot 9c1b213ae8 Update urllib3 from 1.25.5 to 1.25.6 2019-09-30 21:08:09 +02:00
Florian Bruhin a3ec34b55d Further improve release instructions 2019-09-27 13:42:10 +02:00
Florian Bruhin 063fe6f067 Release v1.8.1 2019-09-27 13:35:34 +02:00
Florian Bruhin 32aae4afe2 Update changelog for v1.8.1 2019-09-27 13:33:47 +02:00
Florian Bruhin c09c1fb006 Update to mypy 0.730
We can't use specific type ignores yet as there is no pyflakes release with
this change in: https://github.com/PyCQA/pyflakes/pull/455
2019-09-26 22:29:22 +02:00
Florian Bruhin c397e9326b Go back to Qt 5.12 for tox/pyinstaller
This reverts commit 548b5a17d7.
This reverts commit fe32e00a4e.

Due to QTBUG-77364 (broken keyboard focus), we can't upgrade to qtbase 5.13.1.

However, with 5.13.0 (and QtWebEngine 5.13.1), we run into two more issues:

- Segfaults in QQuickWindowPrivate::updateDirtyNode() when logging into a
  Google account (especially on macOS).
- Qt 5.13.0 with the old PyQt5 exit scheme segfaults on exit on Windows.
  However, pyqt5_enable_new_onexit_scheme() was added in PyQt 5.13.1.

See https://bugreports.qt.io/browse/QTBUG-77364
See https://www.riverbankcomputing.com/news/pyqt-5131
Reopens #4918
2019-09-26 18:33:48 +02:00
Florian Bruhin 4f76266a4b build_release: Ignore another macOS smoke test line 2019-09-26 18:26:35 +02:00
Florian Bruhin db21962d78 build_release: Print uploaded file 2019-09-25 23:23:31 +02:00
Florian Bruhin 8f7e232722 build_release: Improve handling of half-uploaded release 2019-09-25 22:06:46 +02:00
Florian Bruhin 6cd30be9bd build_release: Set asset description directly 2019-09-25 21:17:58 +02:00
Florian Bruhin f2a09a97b2 build_release: Add retry functionality for GitHub upload 2019-09-25 21:09:44 +02:00
Florian Bruhin fe32e00a4e Use Qt 5.13 with mkvenv-pypi 2019-09-25 18:58:08 +02:00
Florian Bruhin 0cbaaa0c93 Update changelog for v1.8.0 2019-09-25 18:56:57 +02:00
Florian Bruhin ebad75f915 macOS: Ignore new smoke test line
See #4919
2019-09-25 17:59:17 +02:00
Florian Bruhin 81b1e7b8a3 update_version: Improve release instructions 2019-09-25 17:54:37 +02:00
Florian Bruhin 0e96747300 Release v1.8.0 2019-09-25 17:43:02 +02:00
Florian Bruhin 548b5a17d7 Revert "Use Qt 5.12 for PyInstaller"
This reverts commit 56a2c50508.

Fixes #4918
2019-09-25 17:42:13 +02:00
Florian Bruhin 2771025aa7 Update content.headers.user_agent for Chrome 76 2019-09-25 17:40:56 +02:00
Florian Bruhin 804d0e445e Update docs 2019-09-25 16:06:08 +02:00
Florian Bruhin ad83f4c340 Add check for missing userscript description 2019-09-25 16:03:42 +02:00
Florian Bruhin d0e8d22ae0 Merge remote-tracking branch 'origin/pr/5031' 2019-09-25 15:44:42 +02:00
Florian Bruhin 2b3a848352 Improve readability-js docs
See #5032
2019-09-24 19:06:55 +02:00
Florian Bruhin ec67039eff Update FAQ 2019-09-24 17:53:27 +02:00
Florian Bruhin 0553e8dcba Update changelog 2019-09-24 17:29:22 +02:00
Florian Bruhin e43ea9efcf Ignore sqlite locking protocol error
According to https://sqlite.org/rescode.html this error should rarely happen:

  The SQLITE_PROTOCOL result code indicates a problem with the file locking
  protocol used by SQLite. The SQLITE_PROTOCOL error is currently only returned
  when using WAL mode and attempting to start a new transaction. There is a
  race condition that can occur when two separate database connections both try
  to start a transaction at the same time in WAL mode. The loser of the race
  backs off and tries again, after a brief delay. If the same connection loses
  the locking race dozens of times over a span of multiple seconds, it will
  eventually give up and return SQLITE_PROTOCOL. The SQLITE_PROTOCOL error
  should appear in practice very, very rarely, and only when there are many
  separate processes all competing intensely to write to the same database.

However, in practice, this happens for some users during the sqlite
initialization (while turning on WAL). Since we can't do anything, this
shouldn't be handled as error.
2019-09-24 17:15:12 +02:00