用车汽车身上那些“疤痕”怎么修复完美如初?

百度   而校方的苦衷似乎也情有可原——一位从教20多年的老校长说,校园非理性现象尤其是校园欺凌的发生,大多发生在课后,老师看不见、家长管不着、门卫顾不上。

The main branch is currently the future Python 3.15, and is the only branch that accepts new features. The latest release for each Python version can be found on the download page.

'19 '20 '21 '22 '23 '24 '25 '26 '27 '28 '29 '30 '31 end-of-life Python 2.7 end-of-life Python 3.6 end-of-life Python 3.7 end-of-life Python 3.8 security Python 3.9 security Python 3.10 security Python 3.11 security Python 3.12 bugfix Python 3.13 prerelease Python 3.14 feature Python 3.15

(See below for a chart with older versions. Another useful visualization is endoflife.date/python.)

Supported versions?

Dates shown in italic are scheduled and can be adjusted.

Branch

Schedule

Status

First release

End of life

Release manager

main

PEP 790

feature

2025-08-04

2031-10

Hugo van Kemenade

3.14

PEP 745

prerelease

2025-08-04

2030-10

Hugo van Kemenade

3.13

PEP 719

bugfix

2025-08-04

2029-10

Thomas Wouters

3.12

PEP 693

security

2025-08-04

2028-10

Thomas Wouters

3.11

PEP 664

security

2025-08-04

2027-10

Pablo Galindo Salgado

3.10

PEP 619

security

2025-08-04

2026-10

Pablo Galindo Salgado

3.9

PEP 596

security

2025-08-04

2025-10

?ukasz Langa

Unsupported versions?

Branch

Schedule

Status

First release

End of life

Release manager

3.8

PEP 569

end-of-life

2025-08-04

2025-08-04

?ukasz Langa

3.7

PEP 537

end-of-life

2025-08-04

2025-08-04

Ned Deily

3.6

PEP 494

end-of-life

2025-08-04

2025-08-04

Ned Deily

3.5

PEP 478

end-of-life

2025-08-04

2025-08-04

Larry Hastings

3.4

PEP 429

end-of-life

2025-08-04

2025-08-04

Larry Hastings

3.3

PEP 398

end-of-life

2025-08-04

2025-08-04

Georg Brandl, Ned Deily (3.3.7+)

3.2

PEP 392

end-of-life

2025-08-04

2025-08-04

Georg Brandl

3.1

PEP 375

end-of-life

2025-08-04

2025-08-04

Benjamin Peterson

3.0

PEP 361

end-of-life

2025-08-04

2025-08-04

Barry Warsaw

2.7

PEP 373

end-of-life

2025-08-04

2025-08-04

Benjamin Peterson

2.6

PEP 361

end-of-life

2025-08-04

2025-08-04

Barry Warsaw

Full chart?

'08 '09 '10 '11 '12 '13 '14 '15 '16 '17 '18 '19 '20 '21 '22 '23 '24 '25 '26 '27 '28 '29 '30 '31 end-of-life Python 2.6 end-of-life Python 2.7 end-of-life Python 3.0 end-of-life Python 3.1 end-of-life Python 3.2 end-of-life Python 3.3 end-of-life Python 3.4 end-of-life Python 3.5 end-of-life Python 3.6 end-of-life Python 3.7 end-of-life Python 3.8 security Python 3.9 security Python 3.10 security Python 3.11 security Python 3.12 bugfix Python 3.13 prerelease Python 3.14 feature Python 3.15

Status key?

Python releases go through five phases, as described in PEP 602. Release managers can adjust specific dates as needed.

feature:

Before the first beta, the next full release can accept new features, bug fixes, and security fixes.

prerelease:

After the first beta, no new features can go in, but feature fixes (including significant changes to new features), bug fixes, and security fixes are accepted for the upcoming feature release.

bugfix:

Once a version has been fully released, bug fixes and security fixes are accepted. New binaries are built and released roughly every two months. This phase is also called maintenance mode or stable release.

security:

After two years (18 months for versions before 3.13), only security fixes are accepted and no more binaries are released. New source-only versions can be released as needed.

end-of-life:

Five years after a release, support ends. The release cycle is frozen; no further changes are allowed.

See also the Development cycle page for more information about branches and backporting.