Repository navigation
re module needs to support bytes / memoryview well #45623
Description
| BPO | 1282 |
|---|---|
| Nosy | @gvanrossum, @benjaminp, @serhiy-storchaka |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2009-02-21.21:05:47.025>
created_at = <Date 2007-10-15.23:26:51.611>
labels = ['type-bug']
title = 're module needs to support bytes / memoryview well'
updated_at = <Date 2014-11-08.20:27:32.486>
user = 'https://github.com/gvanrossum'bugs.python.org fields:
activity = <Date 2014-11-08.20:27:32.486>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = True
closed_date = <Date 2009-02-21.21:05:47.025>
closer = 'benjamin.peterson'
components = []
creation = <Date 2007-10-15.23:26:51.611>
creator = 'gvanrossum'
dependencies = []
files = []
hgrepos = []
issue_num = 1282
keywords = []
message_count = 5.0
messages = ['56472', '82582', '230855', '230872', '230874']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'timehorse', 'benjamin.peterson', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1282'
versions = ['Python 3.0']
Activity
gvanrossum commentedon Oct 15, 2007
Once PEP-3137 is fully implemented, the re module needs to be fixed so
that the regex argument, the substitution argument, and the argument
being searched/replaced are allowed to be arbitrary bytes arrays; where
hashing is needed a copy in an immutable bytes object can be made.
benjaminp commentedon Feb 21, 2009
re has supported bytes for a while now.
serhiy-storchaka commentedon Nov 8, 2014
Actually non-hashable patterns are not supported.
Should it be considered as a bug?
gvanrossum commentedon Nov 8, 2014
Hm, I don't see a reason why the *pattern* should be a bytearray or memoryview, only the string it is searching. But if you fixed it by casting it to bytes I won't stop you. :-)
serhiy-storchaka commentedon Nov 8, 2014
It is easy to fix with small (but non zero) cost, but I don't see a reason too.
So I don't reopen this issue.