Python Insider
blog.python.org · Company blog · on HN since 2011
Python Insider is the official Python core development blog, announcing releases, sprints, security fixes, and packaging changes.
What HN saysHN links it for release announcements like Python 3.13 and free-threaded 3.14, and for security items such as defusedxml and PyPI two-factor authentication.
37HN people shared it
6linked it in comments
50stories submitted
375story points
4 months agolast shared
2011people per year2026
Most-shared posts
- 1Python: defusedxml fixes for XML security issues3 people · 4 points · first shared 2013 · discussion on HN
- 2Python Core Development Sprint 2016: 3.6 and beyond2 people · 34 points · first shared 2016 · 2 comments on HN
- 3Python 3.6.1 is now available2 people · 29 points · first shared 2017 · 1 comments on HN
- 4Python 3.14: Free threaded Python is here2 people · 10 points · first shared 2025 · 1 comments on HN
- 5Upgrade to pip 20.2, plus, changes coming in 20.32 people · 6 points · first shared 2020 · 1 comments on HN
- 6Python 3.13.0 (final) released2 people · 4 points · first shared 2024 · discussion on HN
- 7Python Insider: Python 3.4.0 released2 people · 2 points · first shared 2014 · discussion on HN
- 8Pip 10 has been released1 people · 105 points · first shared 2018 · 27 comments on HN
- 9Python 3.6.7 and Python 3.7.1 are now available1 people · 30 points · first shared 2018 · discussion on HN
- 10Python 3.14.0 is now available1 people · 24 points · first shared 2025 · 11 comments on HN
- 11Python 3.6.2 is now available1 people · 14 points · first shared 2017 · discussion on HN
- 12Python 3.7.4 is now available1 people · 12 points · first shared 2019 · 1 comments on HN
- 13Python Language Summit Report - PyCon 20121 people · 11 points · first shared 2012 · discussion on HN
- 14Python 3.6.0 release candidate 2 is now available1 people · 8 points · first shared 2016 · discussion on HN
- 15Python 3.11.0 is now available1 people · 8 points · first shared 2022 · 2 comments on HN
What HN people wrote when they linked it
lumpa · 2024-10-07
I has officially been released: https://blog.python.org/2024/10/python-3130-final-released.html
kowlo · 2020-11-13
Potentially catastrophic... they've introduced 2FA (https://blog.python.org/2019/05/use-two-factor-auth-to-improve-your.ht… with more to come - this may help!
dalke · 2014-12-02
The base problem is that XML is not secure by default.
Every solution requires either figuring out the problems yourself (which is impossible, given the number of problems that exist), or learning about it from elsewhere. No matter what, there will be people asking the same question you did.
I found out about defusedxml because I read planet.python.org where http://blog.python.org/2013/02/announcing-defusedxml-fixes-for-xml.htm… came up, and because I had enough general understanding of the security problems with XML to recognize why it was created.
yeukhon · 2014-03-19
It won't, not for a long time. http://legacy.python.org/dev/peps/pep-0453/ and http://blog.python.org/2014/03/python-340-released.html
jacobian · 2013-02-19
Yes: Django only uses XML in one very limited place, the serialization parsing framework, which isn't exposed publicly in any way. It's used for data backup/restore as well as for test fixtures, but that's it. Further, the same framework also supports JSON, and it's extremely rare to find a Python developer who's going to chose XML over JSON. So in terms of Django itself the attack surface is extremely small.
That said, if you're parsing XML in your own code you should be looking at defusedxml, also announced today: http://blog.python.org/2013/02/announcing-defusedxml-fixes-for-xml.htm… So maybe we should make a bigger point about that? If you've got suggested edits to the announcement let me know, happy to incorporate 'em.
jlarocco · 2012-03-05
I'm not sure there's a compelling reason to upgrade old, working code to Python 3. The cost of having Python2 and Python3 installed on the same machine is minuscule. The hardest part is making sure scripts use "#!/usr/bin/env python2" or "#!/usr/bin/env python3" appropriately. Even on Windows, the "Python launcher for Windows" [1] will launch the correct version of Python.
My rule of thumb is write new stuff in Python 3, keep old stuff on Python 2 unless I have to rewrite it for some reason anyway.
Upgrading just to upgrade seems like developer problem more than a technical problem.
[1] http://blog.python.org/2011/07/python-launcher-for-windows_11.html