meta_pixel
Tapesearch Logo
Log in
Talk Python To Me

#153: How Python Evolves

Talk Python To Me

Michael Kennedy

Technology

4.8635 Ratings

🗓️ 1 March 2018

⏱️ 82 minutes

🧾️ Download transcript

Summary

If you have spent some time in the Python community, you have probably heard the term PEP which stands for Python Enhancement Proposal. In fact, the very first one was created in June 2000 which defines the PEP process.

Transcript

Click on a timestamp to play from that location

0:00.0

If you spent some time in the Python community, you've probably heard the term PEP, which stands

0:04.6

for Python enhancement proposal. In fact, the very first one was created in June 2000,

0:11.3

and its purpose was to define the PEP process itself. Our guest this week, Nick Coglin,

0:17.1

was a co-author on that very pep and many, many more.

0:25.5

In this episode, we're going to discuss peps and how Python officially evolves,

0:29.5

but also there are many other forces that drive and influence Python.

0:31.8

So let's dig into all of these right now.

0:33.3

This is Talk Python to Me.

0:37.4

Episode 153 recorded February 6th, 2018.

0:51.0

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

0:58.8

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

1:02.5

Keep up with the show and listen to past episodes at TalkPython.fm.

1:06.1

And follow the show on Twitter via At Talk Python.

1:09.2

This episode is brought to you by Linode and Datadog.

1:12.8

Be sure to check out their offers during their segments.

1:14.9

It really helps support the show.

1:17.0

Talk Python Emmy is partially supported by our training courses.

1:20.7

Have you heard about the 100 days of code challenge?

1:23.4

It's a challenge where you write code for an hour a day for 100 days.

1:27.6

It's helped many developers finally master programming, but it can be hard to know what to study

1:33.0

or have resources to focus on.

1:35.5

That's why we wrote not one, but two 100 days of code courses.

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from Michael Kennedy, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Michael Kennedy and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2025.