I think his question is better phrased as, what does any of that mean to him as a user. Insertion order preservation is pretty neat but for the random joe they might not know what some of those things truly offer
I'd like to think that each of those bullet points is either self explanatory by the title in what it offers, or is summarized in the first few lines of the respective PEP. The order preservation already existed in 3.6 as mentioned, so that's also not even "new" bar it is now "officially new".
If they aren't, well, I'd like to hear from someone which ones aren't and I'll apologize immediately and give an explanation that should have been in the PEP.
You assume people actually realize how all of this is organized . Not everyone does . And even if they read it , it’s not always immediately obvious what exactly each of them does for someone
I said it in the previous comment, I'll say it again. Show me one abstract that a buffoon couldn't understand assuming they know the programming concept itself (ex threads), and I will gladly both explain and apologize.
You haven't done this. No one has. Just throwing angry statements my way. Which is doing nothing but proving my point.
I don't want you to explain it, I am just commenting that you're simply wrong. Lots of programmers don't understand those change logs and would like a better more bitesize description of what is new and what has changed.
This isn't a changelog. The changelog is far more intense. If I'm wrong someone would have asked for an explanation by now and made me apologize, saying why they don't understand the simple abstracts. But none have. The abstracts are extremely bitesize, you can't get smaller without losing important info.
I mean...i told you the question might sound stupid to a python user...while Iam just learning it...so is the 3.7 gonna affect 3.6 and should they transit to 3.7?
3.6 isn't going anywhere. You can still use it if you can't or don't want to upgrade to 3.7. But if you're just learning then you aren't going to notice any real difference between the two. The changes are all more advanced features.
3.7 is going to be backwards-compatible with 3.6, at least in most ways that are meaningful to someone who doesn't work on developing the Python interpreter itself -- that means your 3.6 code will still work under 3.7.
You just get access to some new features if you run that code under a 3.7 interpreter.
The abstracts are extremely basic in terms of necessary comprehension. For example,
This PEP proposes adding a new built-in function called breakpoint() which enters a Python debugger at the point of the call. Additionally, two new names are added to the sys module to make the choice of which debugger is entered configurable.
For the breakpoint PEP. For the PEPs that he can't begin to understand, ex, maybe the thread local storage C api, it wouldn't be because he can't understand that abstract. It would be because he can't understand threads, or what a C API is, because he isn't that advanced yet.
So again, I am not going to repeat the abstracts of the PEPs. He can click the damned links. And I'm not his undergrad professor either-- it's not my job to teach him what a thread is, and even if I was nice enough to do so, which I am, he didn't ask that, he asked what these new features are.
An open question was asked, vaguely, and out of apparent laziness. I, just like you, could have responded. I did. When the laziness was further solidified, I put my foot down.
26
u/13steinj Jun 28 '18
...I can't tell if you didn't bother to click the link or what but: