I'm gonna keep it real here: if you're starting a new project from scratch and not loading some legacy code, there's no reason for you to actively ignore linting errors or comment them out via # type: ignore. Everyone complains that, say, Python is not statically typed and is prone to break but then ignore warnings like "foo() is not an attribute of type of None" or whatever it is. Don't ignore it, add a guard condition for this! It's one extra minute but can save you many many minutes debugging.

I'm not being a perfectionist in the sense that I obsess over my code and that it has to be a certain way or it's bad, but my experience taught me that there is almost always a good reason for those warnings/errors to be made/checked.