UUID package coming to Go standard library

Re:UUID package coming to Go standard library by LtWorf on Saturday March 07, 2026 @04:17AM (#47285952)

Yes, in python they break something at every release now. It's terrible. It mostly is because they remove modules from their standard library for no good reasons.

For example they've removed asyncore, their original loop-based module before the async/await syntax existed. All the software from that era needs a total rewrite. Luckily in debian for now the module is provided as a .deb package so I didn't have to do the total rewrite.

edit: as usual on ycombinator, dowvotes for saying something factually true that can be easily verified :D

[ Parent | on HN ]

Re:UUID package coming to Go standard library by Hendrikto on Saturday March 07, 2026 @06:07AM (#47286529)

I think the downvotes are because you did not answer the question you replied to, and instead gave a pretty unrelated rant.

[ Parent | on HN ]

Re:UUID package coming to Go standard library by LtWorf on Saturday March 07, 2026 @08:07AM (#47287314)

I'm explaining that yes, code does break every new python version? Mostly because they touch the stdlib instead of just leaving it be.

[ Parent | on HN ]

Re:UUID package coming to Go standard library by akerl_ on Saturday March 07, 2026 @02:38PM (#47290768)

The thread is about the code in the std lib being a huge amount of work because the code in the std lib needs to be kept working with new language releases.

And then you answered about downstream code breakage totally outside the std lib.

[ Parent | on HN ]

Re:UUID package coming to Go standard library by zahlman on Tuesday March 10, 2026 @03:26AM (#47320076)

The code is under the open-source PSF license. You can vendor or repackage it as you wish rather than rewriting your dependents. The removal is mostly about ensuring that nobody will try to hold them responsible for any more maintenance (plus they can, for example, drop tests and have a faster running test suite).

[ Parent | on HN ]