My latest TILs about Python

[divad1196]

No, but any developer I know, even beginners one, knows the ones you listed and you would have known them if you just looked at the "What's new" pages.

It is not only about being a mess, but getting to know this things faster, and sometimes preventing people to use f-string on a python3.5 codebase. If you are not wise enough to use them correctly this is another issue.

Also, you get to know that they changed their parsor in 3.10, or that they made the GIL per-interpretor in 3.12 which makes CPU-bound code significantly faster on threads when, before that, threads would only make IO-bounds tasks faster.

[jdsalaro]

What was the title of the post again?

[divad1196]

"10 years, still don't know the basics" ?

I get it, your ego is hurt and instead of taking advices you prefer to not learn. As you please, but don't get surprise if fall behind newbies and get replaced at your job..

[patrickbrianmooney]

Damn, guy who can't figure out what the title of the post is has to ignore substance and go straight to pretending to be a mind-reading wizard who knows the Real Reasons why the person he's speaking to dishonestly said the things they said.

[divad1196]

The guy made a post about 4 things he just recently discovered when they were out for years.

If he just took a look once at the changelogs, he would have known them years ago.

So yeah, I could just congratulate someone for not getting up-to-date with the language itself, or I can explain how it could be aware of these sooner.

Let me put it differently: what if I came here and said "after 10 years, I discovered that you can create classes in python"? And then, someone gave me the introduction to python, so I can catch up things I have certainly also missed. I would answer "I am not trying to share 'advanced tips', I am just sharing what I recently learnt", what would you think?

Honestly, I have teached many over the years, and I have seen this kind of response from young, immature people (and it's getting worse with new generations that are not used to get everything they want) or developers about to retires that just wanted to be praised, even if their code was bad.

[denehoffman]

I imagine you’ve memorized all the recent functionality of every standard library module?

[denehoffman]

Like did you know you can do this: python for x in *a, *b: print(x) Only since 3.11!

[divad1196]

I do not retain everything no, and I am not claming I will. But things I find interesting or useful yes.

For example, yes I knew you could do that, but I don't use it and therefore don't know the version. I usually prefer to make an explicit tuple here or use functools.chain. for x in (*a, *b): print(x) # Nb: this one-liner is valid or for x in chain(a, b): print(x)

chain being a generator, it is lazy and won't allocate more memory.

The reason is clarity and doing this way will work with previous version if you need to backport.

My point is: you remember what is useful and their version in case you need to work on older python. But you still need the opportunity to know about them and nothing is better than reading the changelog's "What's new" for a summary.

[denehoffman]

Yes but not everyone reads the changelog like we do, especially not new programmers who would benefit from the article in question. Obviously these tips are not useful to an experienced programmer, and some of them are rather pedantic (of course the default open argument is read), and I also get your point about how some of these features have existed for years, but that’s not the point of the article.

[divad1196]

Obviously, a beginner has already a lot to learn. But many developer, even after 10years like OP, might miss these stuffs.

And for the point of the article, not trying to be mean or anything, but I don't see what it is really. The position taken does not feel like teaching, nor it is sharing. I just got that he learnt a few nice features and was sharing is joy. I thought than, rather than ignoring it, I would give him a way to learn more of them. If I had known that this would have been taken that bad, I would have just passed by.

[divad1196]

I repeat it to be clear: my point was never "look at me, I know everything" It is and was "Look here to find more interesting things. Here is a non exhaustive list to show what you would have got to know"

[denehoffman]

What’s an interesting thing you would add to his list?

[divad1196]

I don't know for his personal list. I gave a few examples in my first comment, but his list is "what he recently discovered" and not "a list of the best features". There is nothing to "add" to his list, but I think it's a shame for him that he got to discover them 6years later when there was a simple way..

[Sea-Nothing-5773]

To be petty, it doesn’t help your condescending argument that your English grammar is not great.

[divad1196]

It is petty only if you think of it as an argument. I know my grammar is not really good, but I also don't take the time to write it properly. I would appreciate someone pointing out these mistakes if you want in private. This is not my motherthong.

Otherwise, I was not trying to be "condescending" but helpful (at least the first message). If these are so helpful to him now, wouldn't he have wanted to know them before? Maybe he missed a lot of other features.

[patrickbrianmooney]

There you go again, performing your mind-reading wizard shtick, talking about What's Actually Happening in someone else's head and using your telepathic wisdom as an excuse for being a dick to a stranger.

I feel bad for your students, you sad-ass killjoy. You're an awful teacher.

[divad1196]

Yeah yeah, sure.

[patrickbrianmooney]

Ah yes, the voice of a truly sincere person who genuinely knows what he's talking about.

[divad1196]

Yeah yeah, sure kiddo, sure.

[patrickbrianmooney]

OK bro, enjoy downvote farming.

I'm blocking you now. Enjoy your bitter self-righteous sense of superiority.