Open leycec opened 1 year ago
Ah jeez 😞 I'm sorry to hear it's been such an annoyance
That is quite the arcane error! That's not one I've seen before, unfortunately (although I do normally stick to just the linux side of the world!)
Let me take a look at your workflow again and see if there's a way I might be able to help (without using this action)
@leycec I've opened a PR that should allow you to check with mypy still, across all OSes in your matrix! https://github.com/beartype/beartype/pull/179
ps i know static type checking is far from perfect, but I do believe it is useful in certain contexts! don't give up on it! 🙇
Ohnoes. It's @leycec, yet again. I've been repeatedly banging @beartype's head against this action without success. My newest quandary is this seemingly Windows-specific non-human-readable error from
docker build
at action setup:I... don't even know what that means. With great reluctance and considerable sighing, I'm disabling this action in our workflow. All of this ultimately consumed far more scarce volunteer time than I actually had. I don't even like static type-checkers. Almost everything they say is a lie, because Python isn't static; Python is dynamic. That's why I maintain a runtime type-checker. I was just doing this to satisfy end user demand for PEP 561 compliance in @beartype – which is to say, for other people.
But... I'm strongly reconsidering everything now. I'll still locally validate @beartype against mypy, because that still works (for the moment). CI-hosted validation appears to be right out, though. I wish mypy and CI got along better. I also wish I was 18 again. Instead, I am 42 and balding. This must be what futility feels like. :bald_man: :face_exhaling: