Issue 36418: urllib.parse.*Result: support _replace for additional computed addresses

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/80599

classification

Title:	urllib.parse.*Result: support _replace for additional computed addresses
Type:	enhancement	Stage:
Components:	Library (Lib)	Versions:	Python 3.8

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	cheryl.sabella, fdrake
Priority:	normal	Keywords:

Created on 2019-03-24 22:05 by cheryl.sabella, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg338762 - (view)	Author: Cheryl Sabella (cheryl.sabella) *	Date: 2019-03-24 22:05
In msg338645 on issue31822, Fred Drake wrote: > Unfortunately, when the implementation [of urllib.parse.*Result] was migrated to use collections.namedtuple (a benefit), the _replace method wasn't extended to support the additional computed addresses for these types. > > That would really be useful. Opening this issue to track that request.

msg338762 - (view)

Author: Cheryl Sabella (cheryl.sabella) * (Python committer)

Date: 2019-03-24 22:05

In msg338645 on issue31822, Fred Drake wrote:
> Unfortunately, when the implementation [of urllib.parse.*Result] was migrated to use collections.namedtuple (a benefit), the _replace method wasn't extended  to support the additional computed addresses for these types.
>
> That would really be useful.

Opening this issue to track that request.

History
Date	User	Action	Args
2022-04-11 14:59:12	admin	set	github: 80599
2019-03-27 13:46:03	fdrake	set	nosy: + fdrake
2019-03-24 22:05:29	cheryl.sabella	create