VA Technical Reference Model v 25.7

Python

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Python is an interpreted scripting and programming language. This standard supports high-level data structures and uses a simplified approach to object-oriented programming and rapid application development. Additionally, this standard contains programming features such as generators and list comprehensions and includes automatic memory management practices. Note: There are several reference implementations of Python, including JPython (Java based) and IronPython (.Net based). This entry does NOT include each of these implementations and they must be requested individually by users of the individual implementations.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.6
Decision Date:	06/18/2025 at 02:12:21 UTC
Introduced By:	TRM Analysis
Vendor Name:	Python Software Foundation

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date
2.5	09/19/2006
2.6.x	10/01/2008	10/29/2013
2.7.3	04/09/2012	01/01/2020
2.7.10	05/23/2015	01/01/2020
2.7.11	12/05/2015	01/01/2020
2.7.12	06/25/2016	01/01/2020
2.7.13	12/17/2016	01/01/2020
2.7.14	09/16/2017	01/01/2020
2.7.15	05/01/2018	01/01/2020
2.7.x	10/19/2019	01/01/2020
3.0	12/03/2008	01/13/2009
3.1	06/27/2009	04/09/2012
3.2	02/20/2011	02/20/2016
3.3.x	09/29/2012	09/29/2017
3.4.0	03/17/2014
3.4.1	05/18/2014
3.4.2	10/13/2014
3.4.3	02/25/2015
3.4.4	12/21/2015
3.4.5	06/27/2016
3.4.6	01/17/2017
3.4.7	08/09/2017
3.5.0	09/13/2015
3.5.1	12/07/2015
3.5.2	06/27/2016
3.5.3	01/17/2017
3.5.4	08/08/2017
3.5.9	11/02/2019
3.6.2	07/17/2017
3.6.3	10/03/2017	12/23/2021
3.6.7	10/20/2018
3.6.8	12/24/2018
3.6.10	12/18/2019
3.6.12	08/17/2020
3.7.x	06/27/2018	06/27/2023
3.8.x	12/18/2019	10/31/2024
3.9.x	10/05/2020	10/31/2025
3.10.x	10/04/2021	10/31/2026
3.11.x	10/24/2022	10/31/2027
3.12.x	10/02/2023	10/31/2028
3.13.x	10/07/2024	10/31/2029

Current Decision Matrix (06/13/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2024

CY2025

CY2026

Future>

Release

2.5

Unapproved