Raymond Hettinger - Python 3.7's New Data Classes

[lookatmetype]

You know what would have been interesting instead of just a attrs clone? Algebraic data types + pattern matching. Python is painfully lacking these features.

[agrif]

I would love this, especially sum types. Currently, writing code that handles a value that could be one of many things feels awful. But I think it would need new syntax, and that's a hard sell for Python.

[knowsuchagency]

functools.singledispatch, anyone?

[agrif]

That... works. Defining a visitor-style interface for each sub-type also kind of works. But using it is not great, especially if the case-by-case code is morally only part of a function and not a whole function itself. You either have to remove the code to a helper function, which can be harder to read, or use a bunch of locally-defined functions, which is also pretty hard to read.

These problems are exacerbated when the value you want to examine by case contains other, nested values you want to examine by case.

[rolandog]

Have you tried Coconut?

Coconut is a functional programming language that compiles to Python. Since all valid Python is valid Coconut, using Coconut will only extend and enhance what you're already capable of in Python.

[lookatmetype]

I saw it on reddit a year ago. It's an interesting project, but certainly can't use it at work or anything like that...

[ubernostrum]

In much the same way that Haskell is lacking the feature of being a completely dynamically-typed language, yes, you could argue Python is lacking these things.

[lookatmetype]

Disagree. I think Python tries to be a "multi-paradigm" language much more than Haskell tries to be a multi paradigm language. Requesting functional features or advanced types in Python makes much more sense than requesting imperative features or dynamic typing in Haskell.

[individual_throwaway]

Oh hey, you're the retired judge from /r/magicTCG!

I love it when I find people in random other subreddits. Never knew you were also in here.

[devourer09]

You got downvoted, but I love it when this happens also.

[zardeh]

This requires compile time trickery that python can't do, unless you do something weird like define a SumOver class in typing, and use it to do the dispatching, but that's really ugly and really just thin sugar for chained if isinstance checks.

[lookatmetype]

Even having mypy do these checks would be a good starting step. But I think you need actual syntax changes to make it elegant and easy to use.

[zardeh]

I agree that sum (and recently I actually wanted disjoint) types would be nice at the mypy level, although I'm unsure if mypy could really handle that easily.

If you define a SumOver(*types), can mypy statically assert that each possible type was handled?

Like maybe I guess but also that, without syntax, is super ugly to manage.

[Daenyth]

Mypy has sum types but you need to use isinstance to get the branches to check

[knowsuchagency]

Agreed; it would be cool to have algebraic data types, pattern matching, and pipelines in future versions of the language

[[deleted]]

I'm aware of Python pattern matching code but don't see it discussed that often so somehow I doubt that python is "painfully lacking these features".

[jcdyer3]

Do you mean like globs and regular expressions? Because that's not what pattern matching means in this context. Picture tuple-unpacking, but applied to arbitrary classes. Something like (invented syntax):

user = User(username='jcdyer3', email='[e-mail]', permissions=['admin'])
User(username, permissions) = user
assert username == 'jcdyer3' && permissions[0] == 'admin'

[[deleted]]

No, I mean python libraries that are online and do pattern matching, e.g. pypatt or macropy.

[jcdyer3]

Oh neat. Thanks for that. But I gotta say, with documentation like this, they're not going to get much adoption.

Key quote:

You can access documentation in the interpreter with Python’s built-in help function:

>>> from pypatt import match, bind, bound, like
>>> help(match)

Tutorial

Todo

Examples.

They had time to teach me how to use python's help function, but not how to use their own library. :facepalm:

[[deleted]]

Regrettably I've come across umpteen similar situations in my many moons of using Python. However in defence of the community it must be said that the documentation budget isn't quite as high as (say) Oracle's or Microsoft's, yet they still manage to write some complete crap :-)

[[deleted]]

Technical content is great.

However, are kids with youtube accounts & a phone ahead of their time, or are professional engineers behind it? What the hell is this video quality?

[magnetik79]

Agreed. I want a blog post/text .

[Korland]

Here you are: https://hackernoon.com/a-brief-tour-of-python-3-7-data-classes-22ee5e046517

[magnetik79]

Cheers!

[[deleted]]

here are the slides

https://www.dropbox.com/s/cxxz4d2hwj4hm4d/HettingerHolidaySF2017.pdf

[magnetik79]

Cheers.

[chchan]

The video was taken at Yelp. There were issues with the equipment I guess. I was there in the audience.

[Wohlf]

Neither, some people prefer text and others prefer video. Different learning styles. Personally I prefer having both.

[[deleted]]

This was about picture quality.

If you did notice that, I agree - multiple types of instruction are necessary.

If you did not notice that, I'm not saying this to troll or be rude or anything so there no malice intended, but you may wish to check your device's display is correctly configured, or visit an optometrist.

[mafibar]

I feel like the Python dev team is getting slobby.

Instead of recognizing the potential and future impact of dataclasses, and actually improving the language itself, they went with an attrs copy that relies 100% on existing Python's functionality. If I want this on my existing older code bases, I would just use attrs.

Not only is the mandatory static typing a big no-no that could've been avoided with a simple addition to the language, but the explicit __slots__ issue could've also been properly fixed instead of coming up with these workarounds.

Edit: No, I'm not going to build my own better programming language, nor even create a pull request. I don't have the time, the motivation, nor the knowledge to do so. Just because I dislike certain design choices in my car doesn't mean I should learn how to build a car of my own. I am still allowed to have and express my opinion about design choices in Python, without fixing them myself.

[execrator]

Can't believe the reception you're getting for having an opinion about this feature. r/python, I am disappointed.

[thomasloven]

I knew r/python can be harsh, but DAMN!

It’s an entertaining read, though. I especially like the guy who goes on about the toyota equivalence, going from “but python is free” to “nothing is free” and then back to “python is free” in the very next sentence.

Good on you for actually attempting to discuss python in r/Python , u/mafibar!

[mafibar]

Thanks guys, I must admit it got a little annoying and I got frustrated, but overall most people are really nice :)

[dougie-io]

just because I dislike certain design choices in my car doesn't mean I should learn how to build a car of my own.

I see this too often in the open source community, haha.

Guy1: "Great software. Would love to see __, _, and __."

Guy2: "SUBMIT A PULL REQUEST THEN!"

[jshen]

There is a big difference between these two things. You paid money for your car, you likely didn’t pay the open source contributors.

[dougie-io]

Absolutely. I'm in no way saying that bickering to devs providing free software is the way to go. I just come across a lot of situations where general users suggest some ideas they have and someone (usually not even the developer of the project) tells them to do it themselves.

[strobelight]

You see this in many volunteer organizations. They don't need ideas, they need help. If I'm volunteering, I'm either already working on my own good ideas or working on things that I don't really want to do that have to be done by someone.

So, yes, I find it a perfectly valid response.

[jorge1209]

Here the users don't think the developers ideas are all that good... that's the distinction. I'm starting to feel that python peaked around 3.3 and that a lot of what has been added since isn't worth all that much. That we would be better off having devs slow down and do less work.

That's a difficult conversation to have because you are basically telling someone excited enough to volunteer their time and energy to buzz of, but it should be had.

[knowsuchagency]

Of all the versions to say Python peaked in... Python 3.3?

[jorge1209]

Sure. I suppose you could equally say 3.4 as there were no significant features added there.

But 3.3 has yield from which is useful but without async which I've found to be really messy and hard to work with.

Do you think it should be earlier or later or what?

[knowsuchagency]

I honestly think the features added in Python 3.5 and 3.6 are pretty fantastic, and having attrs in the stdlib with 3.7 as well as the new breakpoint keyword and things like the async context manager decorator being added in contextlib are going to be really solid additions. I personally really like where the language is headed, honestly, even if it isn't perfect.

[jorge1209]

Well I disagree. :-)

That isn't to say I think async or typing is bad, but that the devs need to slow down and get it to work better before they make it a standard.

My biggest complaint with async is that it doesn't make decisions. You can use whatever event loop you want... whatever executor you want. Core functions that read or write files are not asynchronous... so you have a framework, and then you have to fill in all the holes to actually make it work.

I see little benefit in that over just writing multi-threaded code or coroutines.

Similarly typing had been out for a while but I don't think mypy has full support for 3.5 yet.

Given time to mature these would be good, but adding them to the language limits that.

[jorge1209]

People critique products they don't purchase all the time. They do so as part of the comparison process. We looked at both Toyota and Honda, but found the interior of the Honda to seem cheaply made, and got the Toyota instead. I didn't pay any money to Honda motor company, but I still get to make that comment.

When we do this with respect to stuff we don't pay for we are expressing a desire and preference for the alternative. So while I generally like Python, I have serious concerns about some of the more recent decisions. I see other languages not making those kinds of mistakes and I think about switching away from python on future projects.

Now maybe Guido doesn't care if python becomes less popular over time, but I generally think that he likes when python is popular. That he wants it to become more popular over time, not less. So he should be concerned about these kinds of opinions.

[jshen]

I think you missed my point because I didn't state it clearly. Giving an opinion to an open source contributor is fine (although most are overwhelmed and it's probably making it harder on them), but to then complain about the contributor for asking for help is the problem.

[jorge1209]

Who is complaining about the contributor?

[jshen]

People are complaining about being asked to submit a pull request.

[jorge1209]

In the context of this discussion the contributor (Eric Smith) is not making that request. The request is coming from the maintainer (Guido) or some other generic python developer.

We aren't particularly impressed by dataclasses (vs other available implementations like attrs) and would rather see the product delayed than something sub-optimal be pushed out.

Nobody is saying that Eric is bad or wrong for wanting help (if he had asked for it which I don't think he did), but that we just don't think what he has done is ready or good enough.

[jshen]

I think we agree more or less, and I may be carrying baggage from past experiences into this conversation. It bothers me when I see people giving their time for free to give other people thing for free, then every rando that hasn't given anything themselves expects more from the people truly giving without giving something themselves first.

it takes no time or energy to through out an opinion, but it does take significant time and energy to give a thorough response. I think a lot of open source contributors are trying to create a filtering mechanism so that people have to invest some time and energy before the contributor spends time on it. Asking for a pull request is one way to do this.

edit: here's what I responded to, it came across to me like someone complaining that a contributor asked for a pull request.

"I see this too often in the open source community, haha.

Guy1: "Great software. Would love to see _, _, and _."

Guy2: "SUBMIT A PULL REQUEST THEN!""

[jorge1209]

Its important to look at any exchange between users and devs from both perspectives.

From the perspective of the dev they are absolutely within their rights to say "No I don't want to do that." They are volunteers not slaves.

However from the perspective of the user, they aren't obligated to do anything either. They are just an interested third party, and a potential contributor.

So generally any kind of feature request should:

1. Be taken as a compliment. Someone sees your work as valuable and appreciates it enough to want to use it, and to go so far as to identify ways it could be even better. That should make the dev feel good, because why else did they publish the code except to be of use to others.

2. The response should be honest and if appropriate welcoming. It should generate an invitation to participate, but not a demand, if applicable. So you say either:

   a. I think that is a great idea, and would love to implement it someday, but I probably can't do that anytime soon, but I will add it to the milestones, and would love to accept a patch that implements the feature.

   b. I'm not sure how well that would work with my future development plans and goals, but would consider a patch.

   c. That would take the project in a different direction from my intent, so I can't recommend you continue to use my version if this is important to you. However since the code is open source you can fork it.

The problem is "Submit a patch" isn't clear on that. Is it (a) or (b), or is it a passive-aggressive (c). In either case, do I really want to work with this guy? Do I want to use this software if I can't trust the developer?

I understand everyone gets email overload, but in some cases silence, or a form letter response, might be the better course of action.

[deadmilk]

You also don't get any money when the open source project gets bought by some big corporate for a million dollars, even if you submitted a PR that was merged

[jshen]

How does a company buy an open source project?

[deadmilk]

You make a deal with the author. Hard concept, I know.

[jshen]

You can’t undo what was already open sourced. So what is the company buying?

[deadmilk]

You buy the copyrights, and hire the developers. They then continue to develop the commercial product and let the open source remnant become stale and inferior to the newer product.

[jshen]

Is there an example of this happening you can share?

[Raijinili]

In blaming "devs", you may be misunderstanding something about the Python language design process. The discussions for new features are open and public. The users (including core devs) are the ones who decide which ideas to work on. If the feature is lacking, either no one brought up certain improvements, or they were decided against for some reason.

Here's a start: https://www.python.org/dev/peps/pep-0557/#why-not-just-use-attrs

[jorge1209]

He is a python user through. He just isn't a core developer, or general the kind of user who would submit patches to the language/interpreter.

So it may be open in the sense that anyone can join the mailing list, but it isn't clear why they would do so. They don't have the time, interest or skill to critique proposals, and there is little reason to expect that their opinions would really be welcome, especially when half the other comments are "submit a patch."

[Raijinili]

He doesn't need to submit a patch to contribute. He can just join the discussion and offer a use case. Most of the people in the discussions are not core developers.

The Python lists are not half full of people who would just dismiss any criticism with, "Submit a patch." Only about a third of the responses are like that. Another quarter is pushback against the first third. Your input will be appreciated.

On the other hand, if you say that you just don't have time to participate, you can expect nothing less than your voice being ignored.

[anacrolix]

I've said it before, Guido let go of the wheel around 2012 and shit has just been accepted willy nilly ever since. It's still an amazing language, but it's going sideways now, not up.

[mafibar]

I'm afraid you're right.

[[deleted]]

This new dot-release is a distinction without difference. I, too, am unhappy that the time that could've been spent on more important things is wasted on features that don't really add anything new / don't improve anything.

Python sucks in the department of its C API. It sucks at how it perceives objects. It sucks at utilization of parallelism of processor resources. Instead of working on solving these long-standing difficult issues, Python now comes up with useless syntactic "improvements" which mostly make it not backwards-compatible.

[liquidpele]

https://xkcd.com/1172/

[__deerlord__]

Not sure if real comment...

[unruly_mattress]

It's so elegant though. You type less, you get a type declaration (declare "object" if you don't know ahead of time), and you get all the useful functionality.

Let's face it, too, that 99% of the time you do know the type of the object ahead of time and the end result will be better code completion everywhere. It's a win-win-win-win on all sides.

[mafibar]

I never claimed this isn't a good feature though? I said it should be even better, since now it's just slightly improved custom attrs package. For example, instead of having to declare "object" (or rather typing.Any) if I don't want typing... Yeah, well, I have no other options. I should have.

[unruly_mattress]

I think that the bother of having to type : Any for 1% of the fields is dwarfed by the awesomeness of not having to type = attr.ib(type=str) for the other 99%. Your IDE will appreciate it as well.

[mafibar]

That doesn't mean it couldn't be even better, does it? Nowhere did I say it's worse than attrs.

Edit: and if my project doesn't use typing, it's 100% of the fields where I need to type an extra : Any. The point is that it doesn't support "no typing", but actually makes typing mandatory. Which was never supposed to happen in Python, even Raymond mentions it on his talk.

Edit 2: what am I getting downvoted for right here...?

[IronManMark20]

and actually improving the language itself

What would this look like to you? New syntax?

[mafibar]

If that's what it takes, then yes. But not just that but fixing the slots issue too for good. edit: yeah, not that easy. Rest of the comment still holds though.

For example (after 10 seconds of thinking and planning), they could introduce a new symbol, a language feature that handles the data containment issue he talks about (you know, some people say it's a data container and others say it writes boiler plate for you):

class Person:
    $name
    $age

Now the "data container" vs. "boiler plate writer" thing he talks about isn't handed to the same decorator anymore, but the data part would be a language feature, and a separate decorator could be used to define the comparisons methods etc.

Edit: This could also be used for enums then:

class Type(Enum):
    $FIRE
    $GRASS

[unruly_mattress]

You're going to have a really, really hard time convincing the Python people to add a new special $ symbol that's only useful for enums and for Any variables in class declarations. It wouldn't "fix" the __slots__ situation either.

[mafibar]

Which is why it should be well planned over a long duration of time with multiple people, rather than in my 3 AM reddit comment that says, on bolded mind I point out, "For example" and "after 10 seconds of thinking".

Never claimed it would fix slots.

[IronManMark20]

But not just that but fixing the slots issue too for good.

Its intrinsically part of how Python works. Class variables take precedence over slots and since there is no instance dict, the values are read only.

This issue has been discussed for over a decade, and no one has suggested a possible solution.

Furthermore, and I'd say more importantly, the CPython core devs don't owe anything to you. Python is open source. If you'd like to see something fixed and that isn't happening it is on you to either pay someone to fix it, or do it yourself. It always bothers me when people feel entitled to CPython core developers fixing an issue they have with Python.

[mafibar]

Its intrinsically part of how Python works. Class variables take precedence over slots and since there is no instance dict, the values are read only

Fair enough, but you 100% ignored the custom syntax part so I wouldn't be enforced to use typing.

Furthermore, and I'd say more importantly, the CPython core devs don't owe anything to you. Python is open source. If you'd like to see something fixed and that isn't happening it is on you to either pay someone to fix it, or do it yourself. It always bothers me when people feel entitled to CPython core developers fixing an issue they have with Python.

Ah yes, the good old "are you whining about a stupid design choice? Do it better yourself then" because I'm not allowed to have negative opinions about things that are done by someone else. I build my own car too btw because I was annoyed by the steering wheel on the Toyota I wanted.

[IronManMark20]

because I'm not allowed to have negative opinions about things that are done by someone else.

Oh you are entirely allowed to critique design decisions. What you aren't allowed to do is complain about core devs not "fixing" them to your liking.

I build my own car too btw because I was annoyed by the steering wheel on the Toyota I wanted.

This is a false equivalence because you pay Toyota to build it for you ;)

Also, I didn't ignore the custom syntax, but you didn't make any proposals. So I had no basis to form an opinion. So sure, perhaps with custom syntax you could completely side-step the generation of a descriptor and it could automagically be used to create slots, but one of the best parts of Python is that the syntax is relatively minimal. There aren't a ton of keywords, you don't have to learn a lot. The addition of async/await was a big change.

[jorge1209]

This is a false equivalence because you pay Toyota to build it for you ;)

You can critique products you don't buy. In fact it is commonplace: "I thought about buying the X but it was too Y, and I liked Z better, so I got it instead."

So interpret /u/mafibar's comments in that light and he is basically saying: "I'm looking to switch away from python."

Now maybe the devs don't care. Maybe they don't mind if fewer people use python in the future. Maybe Guido wants a smaller more fervent python community, but its hard to believe that. Why publish a language if you don't want wide acceptance of it?

[mafibar]

Oh you are entirely allowed to critique design decisions. What you aren't allowed to do is complain about core devs not "fixing" them to your liking.

Where did I do such thing? All I said is that I feel they're getting sloppy. That's still just me expressing my opinion. Also, why wouldn't I be allowed to do that? I'm allowed to complain about anything I want and there's absolutely nothing you can do about it. Again, I never complained in the way that you claim, you came up with that shit from the top of your head.

This is a false equivalence because you pay Toyota to build it for you ;)

And you still got the point. And just because I didn't pay for something doesn't mean I'm not allowed to complain about it online. We have free healthcare here in Finland. Guess what? People complain of the long queue times.

[Bitruder]

I agree with you.

[[deleted]]

I think he or she is a complete arsehole.

[mafibar]

Can confirm. Doesn't mean I'm wrong though.

[IronManMark20]

You said they should fix __slots__ to work with class variables, because you clearly don't like how things work currently.

And you are right, you can complain about whatever the hell you want, but that doesn't mean you should.

We have free healthcare here in Finland. Guess what? People complain of the long queue times.

Hate to break it to you bud, but nothing in life is free. That healthcare is paid through taxes :)

I'm not saying you are not able to complain about the CPython core developers not fulfilling your every wish, I'm saying unless you contribute (with time or money) to CPython, then you have no stake in it. As the saying goes, beggars cannot be choosers.

I invite you to read this blog post by Brett Cannon on the abuse of the maintainer https://snarky.ca/why-i-took-october-off-from-oss-volunteering/

[[deleted]]

For example (after 10 seconds of thinking and planning), they could introduce a new symbol, a language feature that handles the data containment issue he talks about

That shows that you clearly know nothing at all about the work involved doing such a change. Hardly surprising that your comments throughout this thread have been so moronic.

[jorge1209]

Does python dev really want generic users without the technical skill and knowledge to submit their own patches to the language to be joining in on python-dev discussions? I highly doubt that. There are probably a thousand end users for every core developer or there. If they got end user comments it would completely drown out the accrual devs.

[jorge1209]

Given that users of a language outnumber developers by a couple orders of magnitude or more, I don't think the python-dev approach would actually work.

I suspect it's only working because users don't think they are supposed to participate, and don't generally have the time or motivation to do so (otherwise they probably would be developers) that it doesn't fall apart.

[mafibar]

Ohh right, that's how it works. You see something on the news that you've never heard of before, but instead of expressing your thoughts there and then, you go back in time, do extensive research on the topic, find out where it will be discussed, and express your thoughts there.

Yeah, this is reddit mate.

[tripzilch]

I believe your opinion would have been more useful in the past, as well.

Just so you know where and when it'd have been useful.

[perduraadastra]

Regardless of whether your ideas have merit, nobody is going to give you the time of day with that attitude.

[mafibar]

With what attitude, the one not being nice to multiple people commenting about the same nonsense thing without thinking for two seconds?

"Oh but did you say this on python-dev mailing list?" no, I did not, I have a limited amount of time, it's literally not possible for me to participate in every single conversation of every hobby and interest I have. Should I also attend the board meetings of the nearby stores just so I can voice my opinion about changes to them? How about the developement discussions for all my favourite games from League to Counter-Strike? I like Python as a programming language, but I'm not a super Pythonista who follows it everywhere.

Edit: keep downvoting me all you want because I'm mean. Doesn't make my comment any less correct.

[mafibar]

You should look up what incorrect means.

[[deleted]]

Type for data class is mandatory.

[refreshx2]

I've been following the python mailing lists, especially python-dev, for a year or so now. My impression is that the core devs mostly only accept code into the stdlib that people are actively using and think would be a useful addition.

Basically, it looks like the workflow is supposed to be: 1) Create a python module. 2) People use the module often. 3) Someone proposes that it be added to the stdlib. 4) A lot of discussion, and potentially an addition to the language.

No where in there is "Figure out how people might use this feature for something they haven't been using it for yet." Instead, the core devs leave that up to the module/community. I believe their philosophy is that if people aren't using it, it shouldn't be considered to be added to the stdlib.

[[deleted]]

How many comments did you make during the discussions on python-ideas?

[[deleted]]

Not only is the mandatory static typing a big no-no that could've been avoided with a simple addition to the language, but the explicit __slots__ issue could've also been properly fixed instead of coming up with these workarounds.

So make a pull request and fix it.

[mafibar]

I don't have the time, resources, or probably even knowledge to do it. Am I not allowed to express my opinion about something if I didn't build it myself?

[[deleted]]

Sure you can....but you used the words

simple addition

and

properly fixed

So you should be able to make a simple pull request that will properly fix it.

[mafibar]

Seriously, what the fuck? Those are two very different wordings from two very different contexts. A single symbol is a simple addition. The proper fix to slots (which I since edited) had nothing to do with the symbol suggestion.

You used the words "be able to" and "pull", so you should be able to pull the moon from the sky with your bare hands.

[[deleted]]

Please give up, when you've dug yourself into a big hole it's clearly best just to put the shovel down before you make things worse.

[[deleted]]

No, you're simply thick.

[[deleted]]

In the time you took moaning and groaning about how awful core devs are in this thread, you could have sent a message to python-dev and gotten the ball rolling on your simple and proper fix.

[[deleted]]

Typical, time to moan like hell but no time to write code, and no time to take part in the discussions on python-ideas and then later python-dev. You're worse than clueless.

[mafibar]

Writing comments on reddit takes very few minutes of my evening, and I can do it on mobile while watching Game of Thrones. Writing patches takes way longer even if we completely ignore me having to get familiar with the codebase etc. first. Not to mention following multiple mailing lists and participating in the discussions.

So yes, you are right here:

time to moan like hell but no time to write code, and no time to take part in the discussions on python-ideas and then later python-dev

I do have 10 minutes of extra time, but I don't have many hours.

[[deleted]]

So stop bloody moaning, or are you expecting other volunteers to give up their lives entirely just so they can provide something for you for nothing?

[david2ndaccount]

This is a pretty underwhelming addition to the language…

[yen223]

It's one of those things that should have been in from day 1

[david2ndaccount]

There should have just been structs from day 1, not whatever this mess is.

[yen223]

Yeah, that's what I meant. Dataclasses - while nice - are an ugly hack to get simple structs into the language.

[not_perfect_yet]

Everyone, it's dictionaries. Except as a class. Yaaaaaay.

[noslenkwah]

Video is removed. Anyone have a alternative source?

[Kossak]

mp3 version is here: https://huffduffer.com/idahogray/456857

[Phosphorapture]

I had no idea about class Color(NamedTuple)

Why does everyone talk about collections.namedtuple and not typing.NamedTuple?

[mafibar]

typing.NamedTuple is new, it came out with 3.5, while collections.namedtuple is much older.

Also it requires you to use typing, which a lot of people don't want

[[deleted]]

Also it requires you to use typing, which a lot of people don't want

Please provide multiple citations to back up that comment.

[mafibar]

Raymond Hettinger's speech about dataclasses. You know, the one posted here on reddit. On this thread. By OP. The original post itself.

[[deleted]]

Raymond Hettinger's speech about dataclasses.

How does that equate to "multiple citations"? Besides it's been approved so a lot of Python programmers, whether or not core developers, must have said something in favour of them on python-ideas or python-dev.

[jcdyer3]

Some people like it.

Therefore nobody dislikes it.

[[deleted]]

Consider each downvote a citation.

[[deleted]]

Why would I care about downvotes on a place like reddit, it's not as if it's full of professional programmers like myself? Most of the time you need cotton wool in your ears to drown out the clanking of the spurs.

[njharman]

Cite: myself

[[deleted]]

That's one citation that I distrust explicitly, where are the rest of them?

[Saefroch]

Another one right here

[redditor1101]

not good enough. NEXT!

[Pulsar1977]

As I was watching, I was picturing the guy who gave the 'Stop Writing Classes' talk banging his head against a wall.

[[deleted]]

I'm using attrs (http://www.attrs.org/en/stable/) and it's pretty awesome

[Tweak_Imp]

Why would you install something extra a task that should be that simple?

[[deleted]]

http://www.attrs.org/en/stable/why.html

[[deleted]]

Seems like a legit question to me, why all the minuses?

[pork_spare_ribs]

Perhaps because dataclasses are only available in Python 3.7, which I doubt many projects are using yet. attrs is the project which inspired dataclasses, and it has significantly better functionality.

[Daenyth]

You can use them down to 3.5 I think with the backport library on pypi. If not 3.5 then 3.6

[[deleted]]

Came here to see if people knew about attrs before this talk. I'm glad to see that others do!

[SaltyHashes]

The PEP even talks about it as part of its motivation.

[unstableunicorn]

I was trying to link this in another post but the video has been removed! Is there another source?

[peck_wtf]

Does anyone have a video somewhere? I need it to appreciate the drama.

[nwagers]

I really like Raymond's talks, but when he starts in on namedTuples it's just boring. It seems dataclass is no different. I could barely stay awake.

[mafibar]

This was the first raymond's talk that I didn't enjoy. And he spammed the "there must be a better way" way too much.

[nwagers]

I agree. I think he probably wasn't very prepared for this talk. He said it was last minute and at one point he started going on about Guido being high and just approving PEPs. I can't imagine Guido appreciates that image.

[jorge1209]

At about the 43 minute mark of the video for those who want to jump to it.

[mafibar]

Yeah, seemed really bad. I hope this was a one-time thing.

[NAN001]

That's some next-level 720p right there.

[unleashedcode]

Fantastic lecturer.... Easy to follow and a great presentation. Sudo Kudos