Комментарии:
i am programming since 10+ years in python and don't understand half of the things you say - but i love how happy you are about your personal stuff ;)
ОтветитьThe new tracebacks remind me of rusts compiler errors
ОтветитьI hope they do something special for the π update
ОтветитьGreat review!
ОтветитьAwesome video! I learned quite a bit and am looking forward to 3.13’s official release even more.
EDIT: Removed the rough timestamps since other comments covered them better.
Holy shit etho reference
ОтветитьI am curious what you think about the suggested tag strings (PEP 750)
Ответитьoh snappers!
ОтветитьMind blowing you maintain the deadsnakes ppa. I never knew that lol
ОтветитьOh yeah, this is the good stuff!
ОтветитьHow are the performance improvements? I recall there being a plan coming from 3.9 to 3.13 to 5x improvement or something? Anything concrete for 3.13?
I guess the JIT is part of that plan, but that doesn't bring any improvements. Impressive that they wrote a JIT which first version isn't slower than the non-JIT, but I was hoping for improvements. Guess I'll have to wait another two versions (we always skip one version so we don't have to migrate 50 applications every year :P).
That new repl 🤤
ОтветитьAwesome video. Good job 👍👍👍👍
Ответитьhell yea -- the pdb thingy is so great! its not tiny its HUGE!
ОтветитьHow come you pronounce "GIL" = "Gee-Eye-Ell" but "JIT" = "Djitt" ? :)
ОтветитьI have a question and I have no one who could answer. So if you feel like answering I’d appreciate it.
System - M1 Max MacBook Pro. I usually use pyenv to manage multiple versions. The issue is with pyenv. Versions installed with pyenv are working slower than either the same system version or manually compiled from the source version. It seems pyenv does not use compile optimizations or smth. Does anyone noticed the same or know how to address?
In the past I have used many times deadsnakes ppa for our Ubuntu machines. Thanks for creating it!
ОтветитьOh man, I'm right there with you on the breakpoint things. I've made a habit of just putting print() on the next line, but I'm excited to break that one.
ОтветитьAny plans for a Python to native code compiler? I really don’t want to distribute Python with Apps or use one of these tools that package up Python. But rather take Python and compile straight to an executable. I have said for ages we need an interpreter, JIT and compiler.
Ответитьgo get yer snacks 🍪
ОтветитьJust wanted to say I appreciate your energy! You seem legitimately charmed with all of the new updates. It's refreshing!
ОтветитьThe breakpoint change yessssssss I can't believe this has been broken for so long
ОтветитьI like `copy.replace`, I think I will use it in my language's typed AST for substitution - I don't mutate because it's easier to reason about immutability, and also because I plan to rewrite my compiler later in Coq for formal verification
ОтветитьBut...did you know that python 3.13 is just one version after 3.12, I didn't see you cover that Mr. Python
Ответить"We can just do Generator[type]" this is the best news for me I'm tired to see those None, None)
ОтветитьThank you so much for this video that let us have a quick overview of the good stuffs! And I am grateful for your hard work. On the subject of Traceback colors, I think you have weird colors because you use the Ubuntu gnome terminal, which modify default colors. If you use a more standard color profile (where blue is encoded blue, black is black and so on) you may have more coherent colors for the tracebacks
ОтветитьGo get your snacks lol
ОтветитьNicee
ОтветитьCool, good video as always. I'm a little torn on the .gitignore being created. Part of me wants to say "why does Python need to know about Git at all?".
In the end you still need a good .gitignore file for the projects you're working on anyway or you'll end up with _pycache_ directories added as well.
Thanks for the in-depth video, Anthony. I'd love to see you discuss how to begin contributing to Python open source project. The open source collaboration ecosystem can be daunting even for intermediate devs with no open source xp.
ОтветитьI'm watching a Python 3.13 highlights video, yet most of the servers at my company still run Python 2, so I hardly use Python 3 at work. xD
ОтветитьVery informative & entertaining xD Thank's a lot for your videos!
ОтветитьCan’t wait to see what‘s new in Python 3.141592653589793238462643383279502884197
Ответить❤
ОтветитьMeanwhile, pytorch just announced support for 3.12 😔😀 will wait another year I guess 😀
The no-gil stuff will probably be quite the hurdle for numpy / torch etc. Fingers crossed
Omg Ethoslab reference? Did I mishear?
ОтветитьAnthony, explain, please this inconsistency in Python basic functions:
- you can convert into string 10 and 10.5 - str(10), str(10.5)
- you can convert into float 10, "10" and "10.5" - float(10), float("10"), float("10.5")
- you can convert to int "10", but not "10.5", WHY? You'll get literal error. This is inconsistency. And because of it one has to use two functions instead of one.
You missed incremental GC 🎉
ОтветитьGreat video as always. Note: I have read that the purple color was chosen because it has equal contrast on both black and white backgrounds. Your purple background is an unfortunate conflict with their color choice. I don’t think that they will change moving forward because white and black backgrounds are much more common. Maybe they will enable users to customize the color in the future.
ОтветитьIs tech controlled by femboys? Like a secretary?
ОтветитьWho’s still using this shit?
ОтветитьThis video earned you a new subscriber.
THX for "quick" review of most changes in 3.13. I look forward to seeing 3.13 available in GCP.
Oh my god - I love Etho! 😂
Ответить