electrum/contrib/requirements/requirements.txt

qrcode
protobuf>=3.12,<4
qdarkstyle>=2.7
aiorpcx>=0.22.0,<0.23
aiohttp>=3.3.0,<4.0.0
aiohttp_socks>=0.3
certifi
bitstring
attrs>=19.2.0

# Note that we also need the dnspython[DNSSEC] extra which pulls in cryptography,
# but as that is not pure-python it cannot be listed in this file!
dnspython>=2.0
requirements.txt support for user only pip requirements 7 years ago			`qrcode`
requirements: pin protobuf "<4" protobuf 4.x introduced breaking changes compared to 3.20. To adapt, we would have to regenerate paymentrequest_pb2.py, using protoc>=3.19.0, however ubuntu does not have new enough protoc. Also, unsure if newly generated paymentrequest_pb2.py would be supported by older versions of protobuf. Best to just wait for things to settle. ``` electrum/__init__.py:20: in <module> from .wallet import Wallet electrum/wallet.py:70: in <module> from . import transaction, bitcoin, coinchooser, paymentrequest, ecc, bip32 electrum/paymentrequest.py:37: in <module> from . import paymentrequest_pb2 as pb2 electrum/paymentrequest_pb2.py:36: in <module> _descriptor.FieldDescriptor( .tox/py3/lib/python3.9/site-packages/google/protobuf/descriptor.py:560: in __new__ _message.Message._CheckCalledFromGeneratedFile() E TypeError: Descriptors cannot not be created directly. E If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0. E If you cannot immediately regenerate your protos, some other possible workarounds are: E 1. Downgrade the protobuf package to 3.20.x or lower. E 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower). E E More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates ``` https://github.com/protocolbuffers/protobuf/blob/ceaae1b6a3acca823acc40380a96f94cecc6e6a9/CHANGES.txt#L47 3 years ago			`protobuf>=3.12,<4`
build: relax qdarkstyle version bound Historically, there have often been (visual) issues with new versions of qdarkstyle. The upper bound restriction was mainly there for this reason: to ~force manually testing new versions. There is no known issue with newer versions atm. Remove the upper bound, as there have not been issues with newer versions recently, and this makes it clear to e.g. packagers that it's fine to use newer versions. Add a lower bound for a version that has been tested in the past and is known to work ok. related https://github.com/spesmilo/electrum/issues/7361 3 years ago			`qdarkstyle>=2.7`
requirements: bump min aiorpcx to 0.22.0 aiorpcx 0.20 changed the behaviour/API of TaskGroups. When used as a context manager, TaskGroups no longer propagate exceptions raised by their tasks. Instead, the calling code has to explicitly check the results of tasks and decide whether to re-raise any exceptions. This is a significant change, and so this commit introduces "OldTaskGroup", which should behave as the TaskGroup class of old aiorpcx. All existing usages of TaskGroup are replaced with OldTaskGroup. closes https://github.com/spesmilo/electrum/issues/7446 3 years ago			`aiorpcx>=0.22.0,<0.23`
Aiohttp must be lower than 4.0.0 5 years ago			`aiohttp>=3.3.0,<4.0.0`
require aiohttp_socks>=0.3 5 years ago			`aiohttp_socks>=0.3`
use certifi directly instead of requests 6 years ago			`certifi`
requirements: require bitstring for lnaddr, cryptography for lnbase 6 years ago			`bitstring`
requirements: specify min 'attrs' version related: #6258 5 years ago			`attrs>=19.2.0`
dependencies: support and require dnspython 2.0, rm monkey patches - dnspython 2.0 requires cryptography 2.6 so we now always require that (no longer a choice between cryptography and pycryptodomex) - test_dnssec.py is deleted as it was testing the monkey-patch related: #6538 4 years ago
			`# Note that we also need the dnspython[DNSSEC] extra which pulls in cryptography,`
			`# but as that is not pure-python it cannot be listed in this file!`
build: relax dnspython version bound The <2.1 pin had been put there as dnspython 2.1 added "poetry" as a build time dep, which pulled in a significant number of transitive dependencies, and it was also causing issues with our appimage build. dnspython 2.2.0 was released since, which no longer needs full poetry, only "poetry-core": https://github.com/rthalley/dnspython/commit/da279dec7e8121c4ff6fc1ea166570888a2bb988 related https://github.com/spesmilo/electrum/issues/7361 3 years ago			`dnspython>=2.0`