Комментарии:
i hope python 3.13 will introduce `__mifflin__`
ОтветитьWaste of time time. Useless video
ОтветитьAnd, step by step python will reach c++
ОтветитьFinally!!! I've been waiting for this to start learning Python.
ОтветитьCan't wait for 3.14 - then we'll have Piithon
Ответитьwhy would anyone hate static typing? I get not using it for scripts and hobby shit, but for real world use cases, I can't imagine maintaining code touched by dozens of people without static typing lol.
Ответитьwhy do these FORKIN' MORONS keep inventing languages that aren't type safe?
then having to go back and add types
GET A BRAINS MORAN!
Finally BATCHED😂
ОтветитьIt would be awesome if you made a video about generic functions!
ОтветитьJust 2 more versions
ОтветитьCan’t wait for Py 3.14
Ответить.... Yawn
ОтветитьHow did you learn about all the python language features you currently know how to use and what motivated you to learn them? Many times I watch your videos and I see you use something that I wasn't aware of before like _slots_ and other items like that.
ОтветитьDo they rename Python to PIthon at Version 3.14?
ОтветитьIs just me or Python is becoming more verbose and confusing over time? I mean, I like the new features but I think the simplicity is being lose on the way
ОтветитьDon't do it. All python libraries aren't supported yet.
ОтветитьMy friend for whatever reason absolutely hates 3.12 down to his core.
ОтветитьI really hope python will be called as Pie-thon when 3.14 is released
ОтветитьI'll be waiting for 3.14
Ответитьnice, more useless features
ОтветитьI need python 4
ОтветитьIf you need these features why use python?
ОтветитьImmortal objects may be useless to most projects, but for those, for which it is a problem, it may resolve a bit PITA.
ОтветитьCan't wait for 3.14 - Python Pi 😊
ОтветитьWhen can we get 3.14thon?
ОтветитьHonestly, generics for a dynamic programming language is like wearing makeup on a face after plastic surgery 😑, personally I use Python for small apps or task automation, coz its dynamic typing makes development super productive. For large projects, I’d prefer to use Go instead of using Python with type hints, it just doesn’t make sense.
ОтветитьWow they really fucked up the typed syntax didn't they 🤮
ОтветитьWow, python has changed a lot. I learned 3.1 and haven't had a reason to keep in the last few years
Ответитьisn't setuptools something like pyinstaller? I've been using pyinstaller my whole life.....
Ответитьlearnt python on 3.7, and now that its EOL a part of me has died inside but thats for the better
ОтветитьCan't wait for python 3.14, python π
ОтветитьStreamlit is not available in python 3.12
Ответитьif they dont do something big for py 3.14 ima be upset
Ответитьim strugle to find pyaudio for this version of python3.12
ОтветитьIMO Python is a janky language, don't like it much
ОтветитьLooking forward to 3.14 version. I hope they gonna call it Pi-thon
ОтветитьNext update: phyton π
ОтветитьLike, seriously, Python's always changing, and I don't get the obsession with adding new stuff. The OG 2.7 was totally fine, was like, the bomb – it was super stable and everyone could use it.
ОтветитьPython 3.7 is now deprecated, huh? Feels weird, since that's the version I started coding on. But ofc it needed to go eventually. Other than it having a special place in my heart, there's no point in holding onto it
ОтветитьNot that I have a use case for it, but I am curious. How do immortal objects actually work? Is there a way from within python to mark an object as immortal or is that fully up to the C implementation to handle - so only code that is partially C can benefit from it atm?
ОтветитьThey are basically copying TypeScript and changing the design a bit.
Ответитьman you are literally the best python programmer i've ever seen
ОтветитьA lot of changes dedicated to typing for a dynamically typed language...
ОтветитьHi James,
if you are gathering points for a new "Nooby Python habits" video, I might have one. Not sure if I missed it in the list or it is just so stupid that you did not think about it. In most of my codes I initialized instance attributes as class attributes instead of initializing them in the __init__() method. Mainly to make the code shorter and more readable. I mean, sure... Those are shared by all instances of a class, but if they are immutable objects they work like instance attributes. I realized my very stupid nooby habit when I created mutable objects (list and dict in my case) which is then shared between all instances. I think for newcomer this behavior is not quite obvious and can lead to silent misbehavior. I thought it is worth mentioning.
Thank you for your great videos. Even considering the statement above, I'd say they made me a quite good Python dev :)
and it doesnt support most libraries
Ответитьwaiting for pi python
ОтветитьI don't like the new `type` keyword, given that `class` already exists. `type` and `class` are functionally ambiguous, IMO.
Ответить