allow string as sep in _Py_strhex_impl ( bytearray.hex() )

Open
#91,208 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by locating _Py_strhex_impl and the implementation of bytearray.hex(), then inspect how the separator argument is currently handled. Done means allowing a string separator as requested while preserving existing behavior; the payload does not name a test file, so locate the relevant bytearray or hex tests before changing anything.

Written by the indexing model from the issue text.

Description

3.11 interpreter-core type-feature
BPO 47052
Nosy @gpshead, @sweeneyde, @arne123

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 = None
created_at = <Date 2022-03-17.21:03:45.219>
labels = ['interpreter-core', 'type-feature', '3.11']
title = 'allow string as sep in _Py_strhex_impl ( bytearray.hex() )'
updated_at = <Date 2022-03-17.21:45:08.249>
user = 'https://github.com/arne123'

bugs.python.org fields:

activity = <Date 2022-03-17.21:45:08.249>
actor = 'Dennis Sweeney'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2022-03-17.21:03:45.219>
creator = 'arne123'
dependencies = []
files = []
hgrepos = []
issue_num = 47052
keywords = []
message_count = 4.0
messages = ['415447', '415450', '415451', '415452']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'Dennis Sweeney', 'arne123']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue47052'
versions = ['Python 3.11']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.