Add information on modernize and futurize

Description

Contributor guide

Tech stack

python

Domain

documentation

Issue type

documentation

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

unclear

Prerequisites

Basic Python knowledgeFamiliarity with Python 2 to 3 migration

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

The issue requests adding information about the 'modernize' and 'futurize' tools for Python 2/3 compatibility, possibly as a separate chapter. Since the repository is a book on supporting Python 3, look at the existing table of contents or chapter structure to determine where to add this content. There are no comments or linked PRs, so the scope is open. A good starting point would be to outline the differences between modernize and futurize, their usage, and how they fit into the migration workflow. Consider adding examples and best practices. The issue is from 2015, so check if the tools have changed significantly.