[issue21378] ImportError: No module named 'concurrent.futures'

Bill Bergmann added the comment: Thank you for your response. The program works as expected. I removed PYTHONPATH settings for 3.4 and 2.7. I'm not sure how those settings were written. I suspect something related to virtualenv, and I will be watching to see if they are written again. When I

[issue21378] ImportError: No module named 'concurrent.futures'

Ned Deily added the comment: FWIW, works for me using the python.org 3.4 64-bin installer. What is the output of: python3 -c 'import sys;print(sys.version)' As Claudiu suggests, check for a concurrent.py shadowing the standard library version. Also, why are you setting PYTHONPATH to include

[issue21378] ImportError: No module named 'concurrent.futures'

Claudiu.Popa added the comment: Do you have a module/file named concurrent.py in your PATH? -- nosy: +Claudiu.Popa ___ Python tracker ___

[issue21378] ImportError: No module named 'concurrent.futures'

New submission from Bill Bergmann: python 3.4 attempting to run example at https://docs.python.org/3/library/concurrent.futures.html 17.4.2.1 $ python3 17_4_2.py Traceback (most recent call last): File "", line 2195, in _find_and_load_unlocked AttributeError: 'module' object has no attribute