Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python 3.13.0 Is Released

docs.python.org

Post reply on HN
Print view View original

51–60 of 135 posts

Re: Python 3.13.0 Is Released

#51

Post by wdroz »

avidphantasm wrote: post #38
csdreamer7 wrote: post #20

Earlier quoted context omitted.

> The language itself is (more than) complex enough already - I hope this focus on implementation quality continues. As do I.

Agreed. I still haven’t really started using the ‘match’ statement and structural pattern matching (which I would love to use) since I still have to support Python 3.8 and 3.9. I was getting tired of thinking, “gee this new feature will be nice to use in 4 years, if I remember to…”

After this month, Python 3.8 will be end-of-life, so maybe you can push internally to upgrade python.

Re: Python 3.13.0 Is Released

#52

Post by fmajid »

almostgotcaught wrote: post #19
CJefferson wrote: post #12

Good to get advanced notice, if I read all the way down, that they will silently completely change the behavior of multiprocessing in 3.14 (only on Unix/Linux, in case other people wonder what’s going on), which is going to break a bunch of programs I work with. I really like using Python, but I can’t keep using it when they just keep breaking things like this. Most people don’t read all the release notes.

> I really like using Python, but I can’t keep using it when they just keep breaking things like this. So much perl clutching. Just curious, since I guess you've made up your mind, what's your plan to migrate away? Or are you hoping maintainers see your comment and reconsider the road-map?

Not the person you are responding to, but my Python 3 migration plan was to move to Go for all new projects.

Re: Python 3.13.0 Is Released

#53

Post by fmajid »

BiteCode_dev wrote: post #43

I still see Python 3.12.7 being the latest one, with 3.13 delayed because of the GC perf regression. The link, for me, points to the 3.13 RC. Am I seeing a cached version and you see 3.13 ? Cause I can't see it on the homage page download link either.

No, they jumped the gun.

Re: Python 3.13.0 Is Released

#54

Post by boarush »

Python version from 3.10 have had a very annoying bug with the SSLContext (something related only to glibc) where there are memory leaks when opening new connections to new hosts and eventually causes any service (dockerized in my case) to crash due to OOM. Can still see that the issues have not been resolved in this release which basically makes it very difficult to deploy any production grade service difficult.

Re: Python 3.13.0 Is Released

#56

Post by cuu508 »

kstrauser wrote: post #35
mg wrote: post #25

Earlier quoted context omitted.

Hmm.. I think this is a misunderstanding. What I meant is: While I am already inside a container running Debian, can I ... 1: ./myscript.py 2: some_magic_command 3: ./myscript.py So 1 runs it under 3.11 (which came with Debian) and 2 runs it under 3.13. I don't need to preserve 3.11. some_magic_command can wrack havoc in the container as much as it wants. As soon as I exit it, it will be gone anyhow. The in a sense,…

The magic command in other settings would be pyenv. It lets you have as many different Python versions installed as you wish. Pro tip: outside Docker, don’t ever use the OS’s own Python if you can avoid it.

> Pro tip: outside Docker, don’t ever use the OS’s own Python if you can avoid it.

Why not?

Re: Python 3.13.0 Is Released

#57

Post by infocollector »

boarush wrote: post #54

Python version from 3.10 have had a very annoying bug with the SSLContext (something related only to glibc) where there are memory leaks when opening new connections to new hosts and eventually causes any service (dockerized in my case) to crash due to OOM. Can still see that the issues have not been resolved in this release which basically makes it very difficult to deploy any production grade service difficult.

Can you please link me to a raised issue for this? This sounds concerning.

Re: Python 3.13.0 Is Released

#59

Post by pkkm »

tightbookkeeper wrote: post #29
pansa2 wrote: post #4

Python versions 3.11, 3.12 and now 3.13 have contained far fewer additions to the language than earlier 3.x versions. Instead the newest releases have been focusing on implementation improvements - and in 3.13, the new REPL, experimental JIT & GIL-free options all sound great! The language itself is (more than) complex enough already - I hope this focus on implementation quality continues.

Removing GIL only increases complexity.

It definitely does, but don't you think that it could be worth it if it makes multithreading usable for CPU-heavy tasks?

Re: Python 3.13.0 Is Released

#60

Post by orf »

boarush wrote: post #54

Python version from 3.10 have had a very annoying bug with the SSLContext (something related only to glibc) where there are memory leaks when opening new connections to new hosts and eventually causes any service (dockerized in my case) to crash due to OOM. Can still see that the issues have not been resolved in this release which basically makes it very difficult to deploy any production grade service difficult.

Maybe related to this segfault I found on MacOS? https://github.com/python/cpython/issues/114653
Post reply on HN