Skip to content

Commit 1b3f580

Browse files
committed
ADR0001: clarify when/where Python 3.6+ is expected
Provide additional context to clarify where we expect Python 3.6+ to be used exclusively (new modules) and link to other discussions around the future of Python 2.7 supporting code. Signed-off-by: Joshua Lock <jlock@vmware.com>
1 parent 71de3f6 commit 1b3f580

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

docs/adr/0001-python-version-3-6-plus.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,11 @@ Technical Story: https://github.com/theupdateframework/tuf/issues/1125
77

88
## Context and Problem Statement
99

10-
We do not want to try and support end-of-life versions of the language.
11-
We want to use modern language features, such as typing.
12-
We want to ease maintainer burden, by reducing the major language versions supported.
10+
We are planning a refactor of tuf where:
11+
12+
* We do not want to try and support end-of-life versions of the language.
13+
* We want to use modern language features, such as typing.
14+
* We want to ease maintainer burden, by reducing the major language versions supported.
1315

1416
## Decision Drivers
1517

@@ -30,10 +32,17 @@ We want to ease maintainer burden, by reducing the major language versions suppo
3032
Chosen option: "Support only Python 3.6+", because we want modern features and lower
3133
maintainer effort as we work to improve our codebase through the refactor effort.
3234

35+
New modules should target Python 3.6+.
36+
3337
Using modules to polyfill standard library features from Python 3.6+ feels
3438
untenable as more libraries are dropping support for EOL Python releases.
3539

3640
### Negative Consequences
3741

3842
* Leaves major adopter and contributor without an actively developed client for some of
3943
their customers stuck on older Python versions.
44+
45+
## Links
46+
47+
* [Discussion of how/where to develop the refactored codebase](https://github.com/theupdateframework/tuf/issues/1126)
48+
* [Discussion of deprecation policy for the pre-1.0, Python 2.7 supporting, code](https://github.com/theupdateframework/tuf/issues/1127)

0 commit comments

Comments
 (0)