Open arkarkark opened 3 years ago
Hmm, it is a dependency if you are using an old version of Python, say 3.5 or so. But otherwise not needed, it installs a dummy in __init__
instead.
But now that old Pythons are no longer supported, I'd like to remove the future_fstrings. The reason I haven't is that I wanted to have a version, say 1.0 that supported older Pythons before moving on.
Perhaps I should speed the process up, although not sure that this pylint problem is a significant problem. Need to think about it a bit.
Maybe I can install the dummy implementation if it isn't installed, rather than by version check, and trust the setup.py to install it.
I found pylint failed on a simple
import console
unless I installed future-fstrings. perhaps that needs to be added as a dependency?here's the output of pylint for a 1 line import file. (on mac OS using brew)