|
1 | 1 | --- |
2 | | -title: "Poetry 2.0 and Python 3.9 Updates" |
3 | | -description: "Upgrading to Poetry 2.0 and Python 3.9" |
| 2 | +title: "Poetry 2.0 and Python 3.10 Updates" |
| 3 | +description: "Upgrading to Poetry 2.0 and Python 3.10" |
4 | 4 | --- |
5 | 5 |
|
6 | | -# Poetry 2.0 and Python 3.9 updates |
| 6 | +# Poetry 2.0 and Python 3.10 updates |
7 | 7 |
|
8 | | -This guide covers important updates to the Python SDK generation process related to Poetry 2.0 and Python 3.9 requirements. |
| 8 | +This guide covers important updates to the Python SDK generation process related to Poetry 2.0 and Python 3.10 requirements. |
9 | 9 |
|
10 | 10 | ## Changes overview |
11 | 11 |
|
12 | 12 | To evolve with the Python ecosystem and maintain compatibility with current tooling, the Python SDK generation process implements two significant changes: |
13 | 13 |
|
14 | | -1. The minimum Python version for generated Python SDKs changes from 3.8 to 3.9. |
| 14 | +1. The minimum Python version for generated Python SDKs changes from 3.9 to 3.10. |
15 | 15 | 2. Poetry packaging tool updates to version 2.0.0. |
16 | 16 |
|
17 | | -## Python 3.9 requirement |
| 17 | +## Python 3.10 requirement |
18 | 18 |
|
19 | | -Python 3.8 reached end-of-life (EOL) status in October 2024 and the Python language maintainers no longer support it for security and bug fixes. The last bug fix update occurred in May 2021, and the last security update occurred in September 2024. |
| 19 | +Python 3.9 reached end-of-life (EOL) status in October 2025 and the Python language maintainers no longer support it for security and bug fixes. |
20 | 20 |
|
21 | | -The key type safety tools used in the Speakeasy generation process have begun removing Python 3.8 support: |
| 21 | +The key type safety tools used in the Speakeasy generation process have begun removing Python 3.9 support: |
22 | 22 |
|
23 | 23 | - Poetry ([change](https://github.com/python-poetry/poetry/pull/9692)) |
24 | 24 | - Mypy ([change](https://github.com/python/mypy/pull/17492)) |
|
63 | 63 |
|
64 | 64 | ## Version update considerations |
65 | 65 |
|
66 | | -Consistent with industry practice, the Speakeasy generator will suggest a minor version update for the generated SDK to reflect these Python changes. However, consider releasing the SDK as a major version update if API consumers are likely to be using Python 3.8, which was previously common for some data management SaaS platforms. |
| 66 | +Consistent with industry practice, the Speakeasy generator will suggest a minor version update for the generated SDK to reflect these Python changes. However, consider releasing the SDK as a major version update if API consumers are likely to be using Python 3.9, which was previously common for some data management SaaS platforms. |
67 | 67 |
|
68 | 68 | For questions, reach out on [Slack](https://go.speakeasy.com/slack). |
0 commit comments