malemburg
commented
23 years ago The docs should contain a note about the codec naming scheme, the use of codec packages and how to address them in the encoding name and some notes about the aliasing support which is available for codecs which are found by the standard codec search function in the encodings package.
Here's a starter (actually a posting to python-dev, but it has all the needed details): """ I just wanted to inform you of a change I plan for the standard encodings search function to enable better support for aliasing of encoding names.
The current implementation caches the aliases returned from the codecs .getaliases() function in the encodings lookup cache rather than in the alias cache. As a consequence, the hyphen to underscore mapping is not applied to the aliases. A codec would have to return a list of all combinations of names with hyphens and underscores in order to emulate the standard lookup behaviour.
I have a ptach which fixes this and also assures that aliases cannot be overwritten by codecs which register at some later point in time. This assures that we won't run into situations where a codec import suddenly overrides behaviour of previously active codecs. [The patch was checked into CVS on 2000-12-12.]
I would also like to propose the use of a new naming scheme for codecs which enables drop-in installation. As discussed on the i18n-sig list, people would like to install codecs without having the users to call a codec registration function or to touch site.py.
The standard search function in the encodings package has a nice property (which I only noticed after the fact ;) which allows using Python package names in the encoding names, e.g. you can install a package 'japanese' and the access the codecs in that package using 'japanese.shiftjis' without having to bother registering a new codec search function for the package -- the encodings package search function will redirect the lookup to the 'japanese' package.
Using package names in the encoding name has several advantages:
- you know where the codec comes from
- you can have mutliple codecs for the same encoding
- drop-in installation without registration is possible
- the need for a non-default encoding package is visible in the source code
- you no longer need to drop new codecs into the Python standard lib
"""
03bde425-37ce-4291-88bd-d6cecc46a30e
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: ```python assignee = 'https://github.com/malemburg' closed_at =
created_at =
labels = ['type-feature', 'expert-unicode']
title = 'Codec naming scheme and aliasing support'
updated_at =
user = 'https://github.com/malemburg'
```
bugs.python.org fields:
```python
activity =
actor = 'lemburg'
assignee = 'lemburg'
closed = True
closed_date =
closer = 'lemburg'
components = ['Unicode']
creation =
creator = 'lemburg'
dependencies = []
files = []
hgrepos = []
issue_num = 225476
keywords = []
message_count = 9.0
messages = ['53058', '53059', '53060', '53061', '53062', '53063', '53064', '53065', '55190']
nosy_count = 2.0
nosy_names = ['lemburg', 'jhylton']
pr_nums = []
priority = 'low'
resolution = 'remind'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue225476'
versions = []
```