UserWarning: Unable to parse file ./foobar.py due to not readable

[jedie]

I get many of this warning with v5.0.0 (Currently the latest available versions)

[timothycrosley]

Hi @jedie,

Thanks for reaching out! Looking at this: jedie/django-user-secrets@84cd1ca I think the reason is that you repleaced --apply with --atomic which do not intend to perform the same function. Apply is now the default so I believe this should be changed to poetry run isort .

[globau]

I see this too when I use the --atomic switch:

  File "/usr/local/bin/isort", line 8, in <module>
    sys.exit(main())
  File "/opt/isort/lib/python3.7/site-packages/isort/main.py", line 702, in main
    for sort_attempt in attempt_iterator:
  File "/opt/isort/lib/python3.7/site-packages/isort/main.py", line 699, in <genexpr>
    for file_name in file_names
  File "/opt/isort/lib/python3.7/site-packages/isort/main.py", line 98, in sort_imports
    **kwargs,
  File "/opt/isort/lib/python3.7/site-packages/isort/api.py", line 282, in sort_file
    **config_kwargs,
  File "/opt/isort/lib/python3.7/site-packages/isort/api.py", line 138, in sort_stream
    compile(output_stream.read(), content_source, "exec", 0, 1)
io.UnsupportedOperation: not readable

[timothycrosley]

@jedie as @globau mentioned this did highlight an error in atomic support in some contexts, which has been fixed in the latest 5.0.3 patch release.

Thanks!

~Timothy