Botocore seems to be causing a really really long ...
# singer-tap-development
v
Botocore seems to be causing a really really long running poetry install, on existing project if you run
poetry update
it seems to be triggered as well. Details in thread
Output from
poetry -vvv install
```Source (PyPI): Getting info for botocore (1.29.69) from PyPI 59: fact: botocore (1.29.69) depends on jmespath (>=0.7.1,<2.0.0) 59: fact: botocore (1.29.69) depends on python-dateutil (>=2.1,<3.0.0) 59: fact: botocore (1.29.69) depends on urllib3 (>=1.25.4,<1.27) 59: derived: not botocore (==1.29.69) 59: fact: no versions of botocore match >1.29.69,<1.29.70 59: conflict: no versions of botocore match >1.29.69,<1.29.70 59: ! botocore (>1.29.69,<1.29.70) is partially satisfied by not botocore (==1.29.69) 59: ! which is caused by "botocore (1.29.69) depends on urllib3 (>=1.25.4,<1.27)" 59: ! thus: botocore (>=1.29.69,<1.29.70) requires urllib3 (>=1.25.4,<1.27) 59: fact: botocore (>=1.29.69,<1.29.70) requires urllib3 (>=1.25.4,<1.27) 59: derived: not botocore (>=1.29.69,<1.29.70) 59: derived: not boto3 (==1.26.69) Source (PyPI): 1038 packages found for boto3 >=1.9,<1.26.69 || >1.26.69,<1.26.70 || >1.26.70,<1.26.71 || >1.26.71,<1.26.72 || >1.26.72,<1.26.73 || >1.26.73,<1.26.74 || >1.26.74,<1.26.75 || >1.26.75,<1.26.76 || >1.26.76,<1.26.77 || >1.26.77,<1.26.78 || >1.26.78,<1.26.79 || >1.26.79,<1.26.80 || >1.26.80,<1.26.81 || >1.26.81,<1.26.82 || >1.26.82,<1.26.83 || >1.26.83,<1.26.84 || >1.26.84,<1.26.85 || >1.26.85,<1.26.86 || >1.26.86,<1.26.87 || >1.26.87,<1.26.88 || >1.26.88,<1.26.89 || >1.26.89,<1.26.90 || >1.26.90,<1.26.91 || >1.26.91,<1.26.92 || >1.26.92,<1.26.93 || >1.26.93,<1.26.94 || >1.26.94,<1.26.95 || >1.26.95,<1.26.96 || >1.26.96,<1.26.97 || >1.26.97,<1.26.98 || >1.26.98,<1.26.99 || >1.26.99,<1.26.100 || >1.26.100,<1.26.101 || >1.26.101,<1.26.102 || >1.26.102,<1.26.103 || >1.26.103,<1.26.104 || >1.26.104,<1.26.105 || >1.26.105,<1.26.106 || >1.26.106,<1.26.107 || >1.26.107,<1.26.108 || >1.26.108,<1.26.109 || >1.26.109,<1.26.110 || >1.26.110,<1.26.111 || >1.26.111,<1.26.112 || >1.26.112,<1.26.113 || >1.26.113,<1.26.114 || >1.26.114,<1.26.115 || >1.26.115,<1.26.116 || >1.26.116,<1.26.117 || >1.26.117,<1.26.118 || >1.26.118,<1.26.119 || >1.26.119,<1.26.120 || >1.26.120,<1.26.121 || >1.26.121,<1.26.122 || >1.26.122,<1.26.123 || >1.26.123,<1.26.124 || >1.26.124,<1.26.125 || >1.26.125,<1.26.126 || >1.26.126,<1.26.127 || >1.26.127,<2.0 60: selecting packaging (23.1) 60: fact: sqlalchemy (1.4.48) depends on importlib-metadata (*) 60: fact: sqlalchemy (1.4.48) depends on greenlet (!=0.4.17) 60: selecting sqlalchemy (1.4.48) 60: derived: greenlet (!=0.4.17) 60: selecting setuptools (67.7.2) Source (PyPI): The cache for boto3 1.26.68 is outdated. Refreshing. Source (PyPI): Getting info for boto3 (1.26.68) from PyPI 60: fact: boto3 (1.26.68) depends on botocore (>=1.29.68,<1.30.0) 60: fact: boto3 (1.26.68) depends on jmespath (>=0.7.1,<2.0.0) 60: fact: boto3 (1.26.68) depends on s3transfer (>=0.6.0,<0.7.0) 60: selecting boto3 (1.26.68) 60: derived: s3transfer (>=0.6.0,<0.7.0) 60: derived: jmespath (>=0.7.1,<2.0.0) 60: derived: botocore (>=1.29.68,<1.30.0) Source (PyPI): 1 packages found for botocore >=1.29.68,<1.29.69 Source (PyPI): The cache for botocore 1.29.68 is outdated. Refreshing. Source (PyPI): Getting info for botocore (1.29.68) from PyPI 60: fact: botocore (1.29.68) depends on jmespath (>=0.7.1,<2.0.0) 60: fact: botocore (1.29.68) depends on python-dateutil (>=2.1,<3.0.0) 60: fact: botocore (1.29.68) depends on urllib3 (>=1.25.4,<1.27) 60: derived: not botocore (==1.29.68) 60: fact: no versions of botocore match >1.29.68,<1.29.69 60: co…
It's not just 0.0.26
If you run
poetry update
on something even from a cookiecutter on 0.0.25 you'll get this.
poetry remove fs-s3fs
fixes it fwiw
botocore
looks to be the offender haven't dove much deeper. @edgar_ramirez_mondragon fyi!
e
urllib3 broke the whole Python ecosystem 😬 . I'm taking a look
h
Yeah, we had to force everything to use
requests==2.29.0
to avoid issues with
urllib3
e