Django has reached a major milestone with its 2.0 release.

This puts Legacy Python that is Python 2 fully in the rearview mirror and brings some nice new features to the framework.

Join me, along with Daniel Roy Greenfeld, to discuss what best practices we should adopt and which ones are still entirely relevant.

This is Talk Python to Me, episode 161, recorded April 23, 2018.

Welcome to Talk Python to Me, a weekly podcast on Python, the language, the libraries, the ecosystem, and the personalities.

This is your host, Michael Kennedy. Follow me on Twitter where I'm at M. Kennedy.

Keep up with the show and listen to past episodes at TalkPython.fmm and follow the show on Twitter via at talk python.

This episode is brought to you by mangaDB and active state. Please check out what they're offering during their segments. It really helps support the show. Danny, welcome to talk by then.

Oh, thanks for having me, Mike. Yeah, it's great to have you here. I've been looking forward to

having you on the show for

quite some time, so we're finally able to put it together, weren't we? Yeah, it's been a few years since we

first started talking. Yes, it's one of the more drawn-out guest appearances, but you're finally here.

And I think the timing is really good because we now have a super major change in the Django world in that we have Django 2, maybe not major in terms of features, but that's a pretty big step to have, you know, go from 1.something to 2.0.

Absolutely. Especially considering that the big change is really under the hood. It's basically the move from Django 1.11 to

2.0 was dropping support for Python 2.7. So from going forward, Django is three and higher.

There's no other way to do it. Should they just made it super explicit and called it Django 3?

I actually have some minor issues with the Django naming structure, and I actually think that

maybe you're right going to Django 3 might have been better. But the beauty of it, though,

is that now the source code is going to be simpler, which means it'll be more stable, it'll be easier for

them to implement more features or for the community to implement more features.

Yeah, anything that attracts more contributors and doesn't chase them away with complexity.

That's a good stuff.

...