A junior developer on your team is preparing to propose a new standard library feature. They ask where they should formally document the motivation, specification, and backward-compatibility implications of their idea so the community can review it. What should you direct them to create?

A blog post on the python.org community forum

A docstring in the existing module

A GitHub issue on the CPython repository

A PEP (Python Enhancement Proposal)

Your team is reviewing a module that contains a mix of `import os`, `import sys`, and `from collections import defaultdict`. According to PEP 8, how should these imports be ordered?

All imports can be in any order as long as they are on separate lines.

`import sys`, `import os`, `from collections import defaultdict`

`from collections import defaultdict`, `import os`, `import sys`

`import os`, `import sys`, then `from collections import defaultdict`

You are writing a public API function `connect(host, port)` and want to document its purpose, parameters, and return value. According to PEP 257, what is the recommended way to write this documentation?

Use a triple-quoted string immediately after the function definition, starting with a one-line summary followed by a blank line and more details.

Write a single-line docstring that includes the full description on one line.

Place a `#` comment above the function definition explaining the parameters and return value.

Use a regular string literal assigned to a variable inside the function.

What is the main purpose of PEP 1?

To list all approved Python libraries

To define the official style guide for Python code

To specify the syntax of the Python language

To explain the purpose, types, and workflow of PEPs

You are reviewing a PEP that proposes a new standard library module. The PEP includes a detailed specification, examples, and a discussion of backward compatibility. According to PEP 1, what is the most important next step for this PEP to move forward?

Publish the PEP on a personal blog to gather informal feedback.

Assign a PEP number and mark it as Accepted immediately.

Submit the PEP to the python-dev mailing list for community discussion and feedback.

Create a pull request on the CPython repository with the implementation.

Python InstitutePCPP1 - Certified Professional Python Programmer 1

Domain 2Objective 1

PCPP-32-101 2.1 Python Enhancement Proposals and Python Philosophy PCPP-32-1 Practice Questions (Page 3)

Part of the Coding Conventions, Best Practices, and Standardization domain, which accounts for 12% of the PCPP-32-1 exam. Python Institute does not publish an official question count, but from its 65-minute exam (~25–45 total, ~3–5 in this domain), expect 1–2 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

5concepts

12%of the exam

Questions 11–15

11application · easy
A junior developer on your team is preparing to propose a new standard library feature. They ask where they should formally document the motivation, specification, and backward-compatibility implications of their idea so the community can review it. What should you direct them to create?
Select an answer first
12application · medium
Your team is reviewing a module that contains a mix of `import os`, `import sys`, and `from collections import defaultdict`. According to PEP 8, how should these imports be ordered?
Select an answer first
13application · medium
You are writing a public API function `connect(host, port)` and want to document its purpose, parameters, and return value. According to PEP 257, what is the recommended way to write this documentation?
Select an answer first
14foundation · easy
What is the main purpose of PEP 1?
Select an answer first
15application · medium
You are reviewing a PEP that proposes a new standard library module. The PEP includes a detailed specification, examples, and a discussion of backward compatibility. According to PEP 1, what is the most important next step for this PEP to move forward?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PCPP-32-1

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Python Institute. “PCPP-32-1” is a trademark of its owner, used for identification only.