What is the primary purpose of a Python Enhancement Proposal (PEP)?

To propose, describe, and track changes or new features for Python

To provide a standardized format for documenting Python code

To list all Python libraries that are officially supported

To enforce coding style rules on all Python projects

Your team maintains a large legacy codebase that does not follow PEP 8. You are tasked with gradually improving code quality without breaking existing functionality. The team has limited time and resources. What is the most effective strategy?

Refactor code to follow PEP 8 only when you are already modifying that code for other reasons.

Ignore PEP 8 for the legacy code and only apply it to new code.

Run an automated tool to reformat the entire codebase at once.

Stop all feature development until the entire codebase is refactored to follow PEP 8.

You are documenting a module that contains a class `BankAccount` with methods `deposit` and `withdraw`. According to PEP 257, what is the recommended format for the module-level docstring?

A docstring inside the `BankAccount` class that describes the entire module.

A single-line docstring that only states the module name.

A comment at the top of the file explaining the module's purpose.

A triple-quoted string at the top of the module that summarizes the module's purpose and lists the main classes and functions.

What does the PEP 20 aphorism 'Readability counts' imply for Python code?

Code should be written to be easily understood by others

Code should use the fewest number of lines

Code should be as short as possible

Code should be optimized for execution speed

What is the main purpose of a docstring according to PEP 257?

To store version control history

To mark code that should be removed in the future

To document the purpose and usage of a code object

To provide a place for the author's name and contact information

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 5)

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 21–25

21foundation · easy
What is the primary purpose of a Python Enhancement Proposal (PEP)?
Select an answer first
22expert · hard
Your team maintains a large legacy codebase that does not follow PEP 8. You are tasked with gradually improving code quality without breaking existing functionality. The team has limited time and resources. What is the most effective strategy?
Select an answer first
23application · easy
You are documenting a module that contains a class `BankAccount` with methods `deposit` and `withdraw`. According to PEP 257, what is the recommended format for the module-level docstring?
Select an answer first
24foundation · easy
What does the PEP 20 aphorism 'Readability counts' imply for Python code?
Select an answer first
25foundation · easy
What is the main purpose of a docstring according to PEP 257?
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.