No
You cannot include GNU Affero GPL v3.0 code in a Python License 2.0-licensed project and ship the result under Python License 2.0. GNU Affero GPL v3.0 requires the combined work to be distributed under GNU Affero GPL v3.0 (or compatible). If your project is meant to stay Python License 2.0-only, do not include GNU Affero GPL v3.0 code in it.
| License | Family | Patent grant |
|---|---|---|
| GNU Affero GPL v3.0 (AGPL-3.0) | network-copyleft | Yes |
| Python License 2.0 (Python-2.0) | permissive | No (implicit at most) |
GNU Affero GPL v3.0: GPLv3 plus § 13: providing software over a network triggers the source-disclosure obligation.
Python License 2.0: Permissive license used by CPython itself; close to BSD.
If you found this page because you're trying to figure out whether shipping a particular dependency is safe, the answer above is a starting point — not a substitute for reading the actual licenses or talking to a lawyer when stakes are high.
LicenseHound walks every transitive dependency in your repo, maps each to its SPDX license, and flags pairs like this one in PR comments. The CLI is free; the team dashboard is paid.