mypy always fails with Python 3.10 match statement

[wrobell]

Please consider:

a = 1
match a:  # type: ignore
    case 0:
        print('is zero')
    case 1:
        print('is one')

then

$ mypy t5.py
t5.py:2: error: Match statement is not supported
Found 1 error in 1 file (errors prevented further checking)

I would expect Mypy to ignore the whole match block.

Or is there an option I am missing, which I can pass to Mypy?

Mypy 0.930, Python 3.10.1.

[srittau]

The match statement is not yet supported in mypy. See #10191.

[wrobell]

@srittau That's OK. I am just asking Mypy to ignore match block, but it still raises the error.

It seems it could be trivial to make it to respect "type: ignore"?

mypy/mypy/fastparse.py

Lines 1289 to 1293 in 9e34f6a

	def visit_Match(self, n: Any) -> Node:
	self.fail("Match statement is not supported",
	line=n.lineno, column=n.col_offset, blocker=True)
	# Just return some valid node
	return PassStmt()

[srittau]

That indeed seems like a regression. At least in mypy 0.910, the match statement could be ignored.

[jarek-webellian]

@srittau downgraded to mypy 0.910, the error is still the same

$ mypy -V && mypy t5.py
mypy 0.910
t5.py:2: error: Match statement is not supported  [syntax]
Found 1 error in 1 file (errors prevented further checking)

[MPalarya]

@srittau is there a way to properly ignore the match section as a temporary solution?
OP's attempt does not seem to work on either 0.910 and 0.931 versions

[srittau]

I'm not sure. I thought it had worked for me with 0.910, but when I downgraded, it failed too.

[intgr]

Looks like proper match support is pretty close to merging (#10191), so I guess it makes sense to just wait it out?

[JelleZijlstra]

It has been merged

[lenoqt]

When this is going to be available on pypi? I am still having issues with my build using the latest version.

[JelleZijlstra]

There are no concrete plans for the next release yet.