plistlib documentation should indicate that it base64-encodes data implicitly

Open
#97,541 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Read the plistlib documentation at https://docs.python.org/3/library/plistlib.html and the referenced implementation in Lib/plistlib.py around line 369. Update the documentation to state that Python bytes values are implicitly base64-encoded in plist data, so users do not encode them beforehand.

Written by the indexing model from the issue text.

Description

docs

Documentation (plistlib)

The plistlib documentation (see https://docs.python.org/3/library/plistlib.html) should indicate that it implicitly base64-encodes plist "data" values (which are indicated by the values being Python bytes objects).
See code at: https://github.com/python/cpython/blob/96f8d3619d839266491b722b943de65892bb0e81/Lib/plistlib.py#L369

The plist file specifications require data values to be encoded with base64. However, I was thinking that I have to do that before using the plistlib, and was wondering what happened (since the data was encoded twice then in the resulting plist file)...

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.