Implement mac_romanian and mac_croatian encodings

Open
#68,231 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue identifies Python's Library (Lib) component but names no files or tests. Start by locating existing mac_* codec implementations and their corresponding tests, then compare the expected patterns for the two requested encodings. Done means both mac_romanian and mac_croatian are implemented and covered by the relevant codec tests.

Written by the indexing model from the issue text.

Description

stdlib
BPO 24043
Nosy @malemburg, @loewis, @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 = None
created_at = <Date 2015-04-23.19:02:04.438>
labels = ['library']
title = 'Implement mac_romanian and mac_croatian encodings'
updated_at = <Date 2015-04-24.19:56:22.706>
user = 'https://bugs.python.org/BehdadEsfahbod'

bugs.python.org fields:

activity = <Date 2015-04-24.19:56:22.706>
actor = 'lemburg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-04-23.19:02:04.438>
creator = 'Behdad.Esfahbod'
dependencies = []
files = []
hgrepos = []
issue_num = 24043
keywords = []
message_count = 8.0
messages = ['241879', '241933', '241971', '241973', '241974', '241975', '241976', '241977']
nosy_count = 4.0
nosy_names = ['lemburg', 'loewis', 'serhiy.storchaka', 'Behdad.Esfahbod']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24043'
versions = ['Python 3.6']

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.