`typing.Literal` can cause false-positive import about autoimport HOT 3 OPEN

I was going to suggest that you showed them the output of autoflake -c script.py but it looks like it's not a good idea, unless you want to open another issue xD

Haha! Yes, that's strange indeed :)
Both autoflake -c script.py and even autoflake script.py seem to be no-ops.

Anyway, I've opened an issue against autoflake: PyCQA/autoflake#109.

If it's critical for you...

It's not super critical -- I'm happy to wait until we hear back from the autoflake folks :P

from autoimport.

Hi @Jasha10 thanks as always for opening the issue. I was able to reproduce the bug, although I think the solution should be done in the upstream library we use to detect import errors. We blindly trust autoflake to detect import errors, and they are giving a false positive with your code when they shouldn't. If it's critical for you, I'm happy to accept a PR to prevent this issue until it's fixed in autoflake. Although maybe it's easier to use the next snippet that works as expected:

from typing import Literal

var: Literal["* time"] = "* time"

What do you think?

from autoimport.

Weird, I've tried to reproduce the error with autoflake --check script.py but it returns no issues even if you run it on the next snippet:

os.getcwd()

Which should say that os is not imported. Nevertheless autoflake.check is what we use to detect the import errors.

I was going to suggest that you showed them the output of autoflake -c script.py but it looks like it's not a good idea, unless you want to open another issue xD

from autoimport.