Python 2.7.* issue
See original GitHub issueI just installed streamlink and I had this error when trying to launch a stream:
Traceback (most recent call last):
File "C:\Program Files (x86)\Streamlink\bin\streamlink-script.py", line 11, in <module>
from streamlink_cli.main import main
File "C:\Program Files (x86)\Streamlink\pkgs\streamlink_cli\main.py", line 17, in <module>
from streamlink.stream import StreamProcess
File "C:\Program Files (x86)\Streamlink\pkgs\streamlink\stream\__init__.py", line 5, in <module>
from .hds import HDSStream
File "C:\Program Files (x86)\Streamlink\pkgs\streamlink\stream\hds.py", line 16, in <module>
from .segmented import (SegmentedStreamReader,
File "C:\Program Files (x86)\Streamlink\pkgs\streamlink\stream\segmented.py", line 1, in <module>
from concurrent import futures
ImportError: No module named concurrent
I had Python 2.7.* (I don’t remember the exact version) and installing Python 3.5.2 fixed the issue. Maybe it was an error on my end, just wanted to point it out in case it might help someone.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Sunsetting Python 2
As of January 1st, 2020 no new bug reports, fixes, or changes will be made to Python 2, and Python 2 is no...
Read more >Extended Support Past Python 2 EOL - ActiveState
Python 2 Security Risks. Without support, Python 2 codebases will continue to become less reliable and more vulnerable as security issues emerge over...
Read more >Continued Use of Python 2 Will Heighten Security Risks
Since 2008, Python 2 and Python 3 together have only had 49 vulnerabilities, with 20 labeled as memory corruption, code execution, or overflows, ......
Read more >Python 2.7 — pip issue installing almost any library - Medium
I found the issue has two reasons: Python 2.7 reach the end of its life on January 1st, 2020; TLS deprecation for pip...
Read more >Python 2 EOL: How to survive the end of Python 2 - InfoWorld
Official bug fixes and security patches for Python 2 will cease. No newly discovered problems in the Python 2 interpreter or the Python...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Because the streamlink pythonscript is using a different shebang, linking to the python3 executable.
No, this is not an error. The Twitch GUI is looking up python independently, so if python2 is listed before python3 in the system’s PATH env var, it will choose this instead. This is all documented in the wiki and also stated in the settings menu next to the input fields. The user is responsible for making sure that streamlink is working with the selected python version.
edit: I have updated the wiki with more details…
It does. As far as I understand it the problem here is that with the way your configuration was setup, the GUI tried to start the python3 version of streamlink with python2.