René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"_wave_parameters in wave.py should be public","articleBody":"**Feature or enhancement**\r\n\r\nMake the named tuple [_wave_parameters](https://github.com/python/cpython/blob/main/Lib/wave.py#L89) public. This nameed tuple defines the inputs to `Wave_write.setparams` which is a public method that users would want to call. To best create an input to setparams one would ideally first make a _wave_parameters named tuple. \r\n\r\nThis is especially true in a typed environment (see https://github.com/python/typeshed/issues/8322) but I feel it would be useful for all users of the wave module.\r\n\r\n**Pitch**\r\n\r\nCurrently if one wants to call setparams in a typed setting, the only option is to use the private type:\r\n```python\r\nimport wave\r\nwith wave.open(\"test.wav\", \"wb\") as wav_file:\r\n    params = wave._wave_params(\r\n        nchannels=1, sampwidth=2, framerate=16_000, nframes=0, comptype=\"NONE\", compname=\"NONE\",\r\n    )\r\n    wav_file.setparams(params)\r\n```\r\nThere is no way to call setparams in a typed environment without using the `wave._wave_params`. If instead it was made public, all users could use the readable version of the parameters above, rather than pass in a tuple without kowing which numbers meant waht.\r\n\r\n**Previous discussion**\r\n\r\nsee https://github.com/python/typeshed/issues/8322\r\n\r\n","author":{"url":"https://github.com/f4hy","@type":"Person","name":"f4hy"},"datePublished":"2022-07-19T02:01:33Z","url":"https://github.com/python/cpython/issues/94991"}