Open RobertCraigie opened 2 hours ago
cc @erictraut do you have any opinions here?
I don't have a strong opinion here, but I worry a bit that removing this check will make it more likely that developers will have stale copies of pyright installed and not realize it.
One option to consider... you could keep the check in place but throttle it so it isn't performed on every invocation. For example, you could throttle it to once a week. That would require you to persist information about the time the last check was performed.
I suspect the latest version warning has caused more pain than usefulness, for a couple of reasons.
--outputjson
which have since been fixed but it's a bit of a whack-a-mole situation and I wouldn't be surprised if other issues crop up in the future.Obviously with features like this one it's very hard, if not impossible, to actually judge how many people this has positively impacted. As such, I'm proposing removing the latest version warning log and if there is an uptick in pyright issues reported by users on an old version, we can consider adding it back in.