News for hackers. Stuff that matters.
Re:Our Plan for Python 3.13 by lacker on Thursday June 15, 2023 @12:54PM (#36343362)
I think it's too late to consider removing the gil from the main implementation.

I think it'll happen one day. Is Python going anywhere?

Give it 20 years. The 2 -> 3 switch will be like the Y2K bug, only remembered by the oldest programmers. The memories of pain will fade, leaving only entertaining war stories. The GIL will still be there, and still be annoying.

Then, when everyone has forgotten, the community will be ready. For an incredibly long and grinding transition to Python 4.

Re:Our Plan for Python 3.13 by ActorNightly on Thursday June 15, 2023 @02:12PM (#36344433)
In 20 years, you wouldn't have Python 4. You will have something like ChatGPT that you interact with and it writes code for you, down to the machine level instructions that are all hyperoptimized. Coding will be half typing, half verbal.
Re:Our Plan for Python 3.13 by jwandborg on Thursday June 15, 2023 @02:36PM (#36344753)
Imagine debugging hyperoptimized machine code. - Or would you just blame yourself for not stating your natural language instructions clearly enough and start over? I guess all of these complex problems would somehow be solved for everyone within the next 21 years and 364 days.
Re:Our Plan for Python 3.13 by ActorNightly on Thursday June 15, 2023 @02:46PM (#36344888)
You wouldn't debug it directly. The interaction will be something like telling the compiler to run the program for a certain input, and seeing wrong output, and then saying, "Hey, it should produce this output instead".

The algorithm will be smart enough to simply regenerate the code minimally to produce the correct output.

Re:Our Plan for Python 3.13 by ilc on Thursday June 15, 2023 @03:30PM (#36345335)
I think you have described a new definition of hell.
Re:Our Plan for Python 3.13 by dumpsterdiver on Thursday June 15, 2023 @05:54PM (#36347143)
Yeah, when people start running into weird failure modes with no insight into the code... sounds like a nightmare.
Re:Our Plan for Python 3.13 by ActorNightly on Friday June 16, 2023 @06:45PM (#36364997)
Input output mapping. Point out what output should be for any failure mode and compiler will auto fix the code
Re:Our Plan for Python 3.13 by m4rtink on Thursday June 15, 2023 @04:22PM (#36345981)
Good luck with that.
Re:Our Plan for Python 3.13 by jamann on Saturday June 17, 2023 @09:16AM (#36369925)
What you wrote is naive. I dont think AI will ever be able to guess what correct output for arbitrary inputs should look like, just based on examples. You need to specify an algorithm that produces the correct output for all inputs. AI could be able to optimize that, but not fill in gaps in the definition of the goal.
Re:Our Plan for Python 3.13 by timacles on Thursday June 15, 2023 @06:32PM (#36347618)
While titillating to think about, what you're describing is more than 20 years away for AI. The best it could do is that for generalized problems, to actually write new original code and complex code is not within the bounds of current AI capabilities.
Re:Our Plan for Python 3.13 by gnulinux on Thursday June 15, 2023 @09:27PM (#36349704)
Yeah, I bet nothing of that sort happens. This programming sci-fi is entertaining to read but it's not grounded in reality.
Re:Our Plan for Python 3.13 by jay_kyburz on Thursday June 15, 2023 @08:05PM (#36348923)
Wat! I'm experiencing 2-3 pain right now! Google has given me till January next year to port all my apps that have been running happily for 10 years. It's no small job either.

I'm already in a state where I can't upgrade to the latest gcloud tools because 2.7 is removed from them. I'm stuck on a version from late last year until I've finished my ports or abandon my projects.

I was a very happy user of GAE standard for many many years, but they burned me in the end and I've learnt my lesson about building on proprietary tools.

Standard frameworks and standard databases for me from now on!

Re:Our Plan for Python 3.13 by ptx on Monday June 19, 2023 @04:04PM (#36395859)
That's 4 years after the EOL of Python 2.7: https://www.python.org/doc/sunset-python-2/