René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Wave stdlib parameter regression in mypy 0.950","articleBody":"\r\n**Bug Report**\r\n\r\nWhen working with the `wave` module of the standard library, valid code from mypy \u003c0.950 works but errors with \r\n```error: Argument 1 to \"setparams\" of \"Wave_write\" has incompatible type \"waveparams\"; expected \"_wave_params\"``` \r\non 0.950+\r\n**To Reproduce**\r\n\r\nUsing Example code \r\n```python\r\n# bug_report.py\r\nimport wave\r\nimport collections\r\n\r\nwaveparams = collections.namedtuple(\r\n    \"waveparams\",\r\n    \"nchannels, sampwidth, framerate, nframes, comptype, compname\",\r\n)\r\n\r\nwith wave.open(\"test.wav\", \"wb\") as wav_file:\r\n    params = waveparams(\r\n        nchannels=1,\r\n        sampwidth=2,\r\n        framerate=16_000,\r\n        nframes=0,\r\n        comptype=\"NONE\",\r\n        compname=\"NONE\",\r\n    )\r\n    wav_file.setparams(params)\r\n```\r\nrunning `mypy` an older version (say 0.931) it says no issues. but using a fully up to date version throws and error of\r\n`error: Argument 1 to \"setparams\" of \"Wave_write\" has incompatible type \"waveparams\"; expected \"_wave_params\"`\r\n\r\nI am not sure why they would be 'incompatible' here. My team was making a namedtuple to make up for the fact that wav_file.setparameters just took a raw untyped tuple as input. \r\n\r\n**Expected Behavior**\r\n\r\nThe named tuple here does match the required fields ofr setparams of `Wave_write` object from the stdlib so it should pass.\r\n\r\n**Actual Behavior**\r\n\r\nOn newer versions of mypy this errors\r\n\r\n**Your Environment**\r\n\r\n- Python version used: 3.8\r\n- Operating system and version: Linux\r\n","author":{"url":"https://github.com/f4hy","@type":"Person","name":"f4hy"},"datePublished":"2022-07-18T05:13:45Z","url":"https://github.com/python/typeshed/issues/8322"}