رونوشت 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 7/6/2024 4:45:55 PM
Duration: 2312.152
Channels: 1
1
00:00:12.865 --> 00:00:23.870
Hello, and welcome to podcast dot in it, the podcast about Python and the people who make it great. When you're ready to launch your next app or want to try a project to hear about on the show, you'll need somewhere to deploy it. So take a look at our friends over at Linode.
2
00:00:24.330 --> 00:00:34.495
With 200 gigabit private networking, scalable shared block storage, node balancers, and a 40 gigabit public network, all controlled by a brand new API, you've got everything you need to scale.
3
00:00:35.180 --> 00:00:43.280
And for those tasks that need fast computation, such as training machine learning models or building your deployment pipeline, they just launched dedicated CPU instances.
4
00:00:44.385 --> 00:00:45.684
Go to python podcast.com/linode,
5
00:00:47.184 --> 00:00:58.670
that's l I n o d e, to get a $20 credit today and launch a new server in under a minute. And don't forget to say thanks for their continued support of the show. And don't forget to visit the site at python podcast.com
6
00:00:59.210 --> 00:01:02.750
to subscribe to the show, sign up for the newsletter, and read the show notes.
7
00:01:03.215 --> 00:01:07.555
And to help other people find the show, please leave a review on iTunes and tell your friends and coworkers.
8
00:01:08.255 --> 00:01:10.994
And to keep the conversation going, go to python podcast.com/chat.
9
00:01:12.460 --> 00:01:17.920
To learn and stay up to date with what's happening in artificial intelligence, check out this podcast from our friends over at the changelog.
10
00:01:18.780 --> 00:01:44.365
Practical AI is a show hosted by Daniel Whitenak and Chris Benson about making artificial intelligence practical, productive, and accessible to everyone. You'll hear from AI influencers and practitioners, and they'll keep you up to date with the latest news and resources so you can cut through all the hype. As you were at the, Thanksgiving table with your your friends and family, were you talking about the fear of AI? Well, I I wasn't at the Thanksgiving table because my wife has forbidden me from doing so.
11
00:01:44.745 --> 00:01:52.500
Oh, I It's it's off limits for for me, lest I drive her insane because I never stop. New episodes premiere every Monday. Find this show at changelaw.com/practicalai
12
00:01:53.920 --> 00:01:55.075
or wherever you listen to
13
00:02:01.155 --> 00:02:08.930
podcasts. You listen to this show to learn and stay up to date with the ways that Python is being used, including the latest in machine learning and data analysis.
14
00:02:09.950 --> 00:02:16.085
For even more opportunities to meet, listen, and learn from your peers, you don't want to miss out on this year's conference season.
15
00:02:16.865 --> 00:02:21.900
We have partnered with O'Reilly Media for the Strata Conference in San Francisco on March 25th
16
00:02:22.440
Load full transcript
--> 00:02:25.980
and the Artificial Intelligence Conference in New York City on April 15th.
17
00:02:26.545 --> 00:02:31.765
In Boston, starting on March 17th, you still have time to grab a ticket to the enterprise data world.
18
00:02:32.065 --> 00:02:35.605
And from April 30th to May 3rd is the Open Data Science Conference.
19
00:02:36.180 --> 00:02:37.400
Go to python podcast.com/conferences
20
00:02:39.220 --> 00:02:52.235
to learn more and to take advantage of our partner discounts when you register. Your host as usual is Tobias Macy. And today, I'm interviewing Naomi Seeder about her career and contributions in the Python community. So, Naomi, could you start by introducing yourself?
21
00:02:52.620 --> 00:02:54.240
Sure. I'm Naomi Seeder.
22
00:02:54.940 --> 00:03:00.480
Currently, I serve as the chair of the board of directors of the Python Software Foundation.
23
00:03:01.485 --> 00:03:06.625
I'm also the leader of a development team that works in Python for Dick Blick Art Materials.
24
00:03:07.165 --> 00:03:07.665
And,
25
00:03:08.445 --> 00:03:15.770
I have a 3rd edition now out now of my book, The Quick Python Book. And do you remember how you first got introduced to Python?
26
00:03:16.150 --> 00:03:22.285
Indeed I do. This is a story that I'm fond of telling, although it does make me seem
27
00:03:22.745 --> 00:03:25.085
really old, which I suppose I am.
28
00:03:25.545 --> 00:03:26.505
And that is,
29
00:03:26.905 --> 00:03:27.645
it was
30
00:03:28.070 --> 00:03:30.070
actually at a Linux fest,
31
00:03:30.390 --> 00:03:33.530
in Moscone Center in San Francisco in 2, 001.
32
00:03:34.630 --> 00:03:37.232
I was the tech director at a school, and,
33
00:03:37.700 --> 00:03:40.855
my assistant and I had been allowed to go out to,
34
00:03:42.375 --> 00:03:44.450
Linux fest for the tutorial
35
00:03:44.750 --> 00:03:52.530
days. We weren't actually allowed to stay for the whole conference. We had to get back and cover things at school. But that meant though that we could attend
36
00:03:53.635 --> 00:03:59.335
a day long tutorial by this guy, Guido van Rossum, who was talking about his language Python.
37
00:03:59.635 --> 00:04:04.189
So I actually learned Python from Guido himself the first time,
38
00:04:04.650 --> 00:04:06.730
back in 2, 001. That was,
39
00:04:07.209 --> 00:04:08.430
Python 2.1,
40
00:04:09.129 --> 00:04:09.785
I believe.
41
00:04:10.105 --> 00:04:17.485
And it's yeah. It's always great having the opportunity to talk to people who've been using Python for so long into its history because
42
00:04:17.865 --> 00:04:18.105
as,
43
00:04:18.780 --> 00:04:26.695
I guess, relative newcomer to the language, I don't have as much of the context of some of the history and evolution of Python and where it came from. So
44
00:04:26.995 --> 00:04:45.414
I'm curious what it is about Python in particular that has persuaded you to spend so much of your time and energy on the language and the community as opposed to any of the innumerable other tools or platforms that you could be spending your time with? Yeah. That's actually something I've wondered about myself.
45
00:04:45.715 --> 00:04:50.215
Back in in in the old days, even in the nineties and whatever, there seemed to be,
46
00:04:50.650 --> 00:04:56.270
new languages, new technologies coming around quite a bit. And when I started doing Python,
47
00:04:57.130 --> 00:05:01.615
I really liked it because of, I was in education and it was,
48
00:05:02.175 --> 00:05:07.880
a great teaching language, particularly compared to something like C or something like Java. But,
49
00:05:08.320 --> 00:05:12.500
I did at the time kind of expect that this would be an interesting thing
50
00:05:13.120 --> 00:05:18.645
that then probably another interesting thing would come along and this wouldn't last so long.
51
00:05:18.945 --> 00:05:20.485
And I think
52
00:05:20.865 --> 00:05:22.165
I would say for
53
00:05:22.544 --> 00:05:26.245
the the reasons that I stayed with with Python so long,
54
00:05:26.660 --> 00:05:28.040
were kind of a combination.
55
00:05:28.660 --> 00:05:35.960
The language continued to grow and develop so that it has stayed relevant for things that I need to do
56
00:05:36.525 --> 00:05:38.385
in terms of handling data,
57
00:05:38.685 --> 00:05:46.139
presenting things via web interface, just just various things. But at the same time, I think it was
58
00:05:46.440 --> 00:05:50.539
the attention paid even from the early days to the notion of community.
59
00:05:50.905 --> 00:05:53.165
And then the way that that has developed,
60
00:05:53.625 --> 00:05:54.125
that,
61
00:05:54.745 --> 00:05:57.965
is really something that is very, very attractive.
62
00:05:58.345 --> 00:05:59.005
I know
63
00:05:59.400 --> 00:06:04.860
sometimes I'm associated with the quote because quite frankly, I stole it with his permission,
64
00:06:05.640 --> 00:06:10.875
from, Brett Cannon. But the notion that I came for the language, I stayed for the community,
65
00:06:11.255 --> 00:06:12.475
I think resonates
66
00:06:13.014 --> 00:06:39.010
with a lot of people, and I know it certainly has always resonated for me. Yeah. I can definitely agree with that sentiment, and I've heard it echoed a number of times and it still rings true. And I was actually just having a conversation recently with somebody about how it's kind of anomalous, the degree of sort of goodwill and community that has developed around this language versus something like Java that has much more of a sort of corporate
67
00:06:39.315 --> 00:06:39.815
progenitor
68
00:06:40.514 --> 00:06:54.560
where you don't really think about somebody going to a Java conference per se. There might be subprojects within that language community that have a vibrant ecosystem of people who are dedicating their time to it. But as a language itself,
69
00:06:54.860 --> 00:07:05.405
there aren't really that many cases where this many people have rallied around it and built up this
entire sort of culture of friendship and openness
70
00:07:05.810 --> 00:07:06.550
and collaboration.
71
00:07:07.170 --> 00:07:19.815
You know, there are definitely other languages that do have that, but it's not as common as you might think if your first language is Python and your first exposure to a community is the Python community. Yeah. I think that's quite right. I mean, I I know I've heard,
72
00:07:20.515 --> 00:07:31.530
some positive things from people about, like, the Go community and stuff like that. But just, I think we've basically created kind of a virtuous cycle here. A lot of people now,
73
00:07:31.910 --> 00:07:35.125
are exposed to the language because of the strength of the community.
74
00:07:35.425 --> 00:07:52.675
And 1 of the first things they then want to do, maybe when they go back to their own communities, is replicate that. So that's that's a very powerful thing. And having used Python for so much of your career, I'm wondering what your primary uses of it are in your current day to day role.
75
00:07:53.455 --> 00:08:00.435
So partly, I, lead a a team of engineers. So I do a certain amount of code review
76
00:08:01.520 --> 00:08:02.740
in in Python
77
00:08:03.040 --> 00:08:03.540
and
78
00:08:04.240 --> 00:08:09.139
not so much production coding, but I also do a lot of what should I say?
79
00:08:10.055 --> 00:08:10.955
Kind of utility
80
00:08:11.495 --> 00:08:13.035
and glue type programming,
81
00:08:13.735 --> 00:08:16.875
extracting reports, being able to move data around,
82
00:08:17.335 --> 00:08:21.240
being able to sometimes do a proof of concept on a process,
83
00:08:21.780 --> 00:08:38.760
things like that. So I do actually code in Python pretty much every day even though my primary role is is more management leadership. As you mentioned, you are the current chair of the board of the PSF and have been for a few years now. So I'm wondering what your primary responsibilities
84
00:08:39.140 --> 00:08:40.360
are in that position
85
00:08:40.820 --> 00:08:46.200
and some of the activities that you're engaged with, you know, within a given week or month.
86
00:08:46.625 --> 00:08:58.120
So I get asked this a certain amount, and I guess the first thing I always say is, well, it's probably not as glamorous as you imagine. But basically the role of the chair of the board is
87
00:08:58.820 --> 00:09:00.200
to make sure that
88
00:09:00.660 --> 00:09:10.470
the board has what it needs to function, to make sure that we have meetings set up and that we have agendas for the meetings, to make sure that we're fulfilling our responsibilities
89
00:09:11.010 --> 00:09:13.190
of of kind of management and oversight.
90
00:09:13.490 --> 00:09:16.390
I also am sort of the direct point of contact
91
00:09:17.014 --> 00:09:17.995
for Eva Yalowska,
92
00:09:18.375 --> 00:09:19.514
our executive
93
00:09:19.815 --> 00:09:20.315
director.
94
00:09:20.935 --> 00:09:21.435
So,
95
00:09:22.295 --> 00:09:26.520
she reports to the board, but you can't have 13 bosses. So in effect,
96
00:09:27.080 --> 00:09:38.295
she talks to me a lot. So we spend a fair amount of time consulting on kind of day to day operations, things like that. And then there are various questions that come up into,
97
00:09:38.995 --> 00:09:41.714
our various mailing lists and things like that where
98
00:09:42.540 --> 00:09:47.360
and we need to be sure that we have have some kind of response from the board.
99
00:09:47.980 --> 00:09:48.480
And
100
00:09:49.020 --> 00:09:50.880
I see it as kind of my responsibility
101
00:09:51.485 --> 00:10:03.610
to lead that and make sure that that happens whether or not it's my opinion, but still that we actually do come forward with with some kind of response as needed. And there are a lot of times where I've been in conversations
102
00:10:04.310 --> 00:10:07.315
where the PSF comes up and there is initially
103
00:10:07.855 --> 00:10:08.995
maybe some confusion
104
00:10:09.295 --> 00:10:12.995
or misunderstanding about the role of the PSF
105
00:10:13.295 --> 00:10:15.395
in relation to the Python language
106
00:10:15.720 --> 00:10:17.579
and some of the activities
107
00:10:18.040 --> 00:10:19.579
and just overall
108
00:10:19.959 --> 00:10:20.459
engagement
109
00:10:21.560 --> 00:10:23.019
of what happens in the PSF,
110
00:10:23.645 --> 00:10:31.265
as it relates to your day to day Python developer or people working on various open source projects or different community events?
111
00:10:31.770 --> 00:10:34.430
Yeah. I I think that's quite true, actually.
112
00:10:35.050 --> 00:10:35.450
And,
113
00:10:36.250 --> 00:10:38.750
I think the first point is that the PSF
114
00:10:39.144 --> 00:10:42.685
does not have anything to do with the decisions
115
00:10:43.065 --> 00:10:44.045
taken on
116
00:10:44.505 --> 00:10:45.245
the actual
117
00:10:45.785 --> 00:10:47.005
design and implementation
118
00:10:47.385 --> 00:10:48.765
of Python the language.
119
00:10:49.769 --> 00:10:50.509
That is
120
00:10:50.889 --> 00:11:19.555
the core developers. And of course, there's been a lot of attention on that lately as they have worked on and started to implement a new governance model. We support them. And honestly, I expect our connections to grow even closer over time, but we do not have any say so over yes or no on the Walrus operator or something like that. That's not our department. On the other hand, what we do do is that we hold the intellectual property
121
00:11:19.935 --> 00:11:22.995
of Python and the trademarks for Python
122
00:11:23.375 --> 00:11:23.875
and
123
00:11:24.350 --> 00:11:26.850
for Python and all of those things.
124
00:11:27.390 --> 00:11:27.890
And
125
00:11:28.990 --> 00:11:29.970
this is actually
126
00:11:30.589 --> 00:11:35.074
a pretty important job because we couldn't really have an open source language unless
127
00:11:35.375 --> 00:11:41.555
somebody made sure that we had the rights to all of those bits that go out as, say,
Python.
128
00:11:42.390 --> 00:11:43.850
So, so that's definitely,
129
00:11:44.710 --> 00:11:51.130
an important function, but probably we spend more time on just managing and fostering the community.
130
00:11:51.875 --> 00:11:52.375
So
131
00:11:52.755 --> 00:11:53.575
we give
132
00:11:54.595 --> 00:11:56.775
quite a bit of money. I think we're approaching
133
00:11:57.555 --> 00:12:16.690
$300, 000 this year supporting Python community events around the world. So, you know, as, as community is an important part of what makes Python Python, that's what we spend, I'd say, the vast majority of our time on is how we can support that, how we can move those things forward, what we can do to help that
134
00:12:17.070 --> 00:12:18.690
inclusive global community
135
00:12:19.150 --> 00:12:24.735
grow and thrive. And for somebody who is just using Python to build a web application
136
00:12:25.115 --> 00:12:28.415
or manage their servers or do some data analysis,
137
00:12:28.795 --> 00:12:32.130
what are some of the ways that they can most effectively
138
00:12:32.510 --> 00:12:35.889
engage with the PSF or help support its mission or,
139
00:12:36.510 --> 00:12:40.105
even just talk to somebody to get a better under get a better understanding
140
00:12:40.405 --> 00:12:42.825
of what its goals and priorities are?
141
00:12:43.685 --> 00:12:44.185
So
142
00:12:45.125 --> 00:12:50.440
to kind of unroll those, I guess, from the back To find out more about the PSF,
143
00:12:51.780 --> 00:12:53.240
you can visit python.org/psf,
144
00:12:54.980 --> 00:13:00.005
and that is kind of our landing page. We also have a mailing list, psfpython.org.
145
00:13:01.905 --> 00:13:04.645
That that's kind of an inbound address for anything
146
00:13:05.185 --> 00:13:06.245
PSF related.
147
00:13:06.980 --> 00:13:12.840
So if you have any questions, the board sees that, our staff see that. So that's kind of a
148
00:13:13.620 --> 00:13:19.285
starting point in terms of how you can find out a little bit more. In terms of becoming
149
00:13:19.825 --> 00:13:26.570
involved, it's kind of a 2 pronged thing for people who have time and inclination to
150
00:13:26.870 --> 00:13:31.850
get involved with events and organizing and helping things happen. I always say
151
00:13:32.230 --> 00:13:39.205
it's kind of think globally, but act locally. That is the best way to get involved is to find
152
00:13:39.665 --> 00:13:41.685
the meetup that is in your area,
153
00:13:42.120 --> 00:13:42.780
the Python
154
00:13:43.240 --> 00:13:46.060
user group, whatever it might be, and
155
00:13:46.440 --> 00:13:51.740
help those events grow. If there is no such thing in your area, then
156
00:13:52.105 --> 00:13:58.845
please contact us and we'll try to help you figure out maybe how you can start a meetup. 1 thing that people don't realize
157
00:13:59.270 --> 00:14:15.584
is that the PSF does support meetup fees for a Python meetup since that's usually a pretty effective way of getting the word out. We we don't want to people have to pay those fees themselves. So so that's 1 thing we can do to help people get started or even continue.
158
00:14:15.960 --> 00:14:25.625
Supporting the PSF directly. Like maybe you've heard that, Oh, PSF sponsors lots of things in Africa and South America. And I think that's great. I'd like to help out. You can become
159
00:14:26.644 --> 00:14:29.065
a supporting member for a $99
160
00:14:29.445 --> 00:14:30.105
a year
161
00:14:30.565 --> 00:14:49.545
and stay tuned. Cause I think we're going to be adding some other options to that in the fairly near future. But so you can actually become a member of the PSF that way, which gives you the right to vote in elections, vote for board members and things like that. So that certainly helps. And at a minimum, I always encourage people to just go to
162
00:14:49.925 --> 00:14:50.425
python.org/psf,
163
00:14:52.079 --> 00:15:15.440
find the membership thing and just sign up as a basic member. That's free, but it helps us kind of keep in touch with you. It gives us an idea of the level of support we've got. And then, you know, maybe later you can decide to do something more. So so those are are some of the things that you can do. Certainly, as I say, please feel free to contact us. And board members and various people from PSF
164
00:15:15.900 --> 00:15:28.300
try to make it to conferences as well. When we do, we're there for people to talk to us. So again, don't hesitate to come up and and talk to a PSF member or board member if you spot 1, at a conference.
165
00:15:28.680 --> 00:15:40.095
And how much of the overall success of the Python language and the growth of the community do you think is directly attributable to the PSF and the support that they provide versus the,
166
00:15:40.555 --> 00:15:42.814
overall ethos of the language
167
00:15:43.150 --> 00:15:49.170
and the people who engage with it? It's it's really hard to separate those 2. I think that
168
00:15:49.550 --> 00:15:54.245
to get where we are now, where we are arguably
169
00:15:55.425 --> 00:15:58.885
1 of, at least 1 of the top 5 languages in popularity,
170
00:15:59.345 --> 00:16:03.220
probably higher than that on most people's scales. I think to get
171
00:16:03.920 --> 00:16:04.500
there without
172
00:16:04.960 --> 00:16:05.700
the community
173
00:16:06.080 --> 00:16:06.580
and
174
00:16:06.960 --> 00:16:10.500
to have the community, I think that's really been the work of the PSF.
175
00:16:11.095 --> 00:16:21.720
Without that part, I don't think we would be there. I think you can find lots of examples throughout history of technically good ideas that never quite made it for other reasons.
176
00:16:22.340 --> 00:16:22.840
So,
177
00:16:23.220 --> 00:16:27.560
I think, yes, the the language is great, but without the support of the community.
178
00:16:28.105 --> 00:16:48.635
And again, I I have a hard time distinguishing the community from the PSF. They seem to be
sort of 2 sides of the same thing. But without that, I don't think we would be where we are today. No. And I think to the fact that there is this organizational structure at the core of the Python community that is there to help keep an eye out to the long term versus
179
00:16:49.095 --> 00:16:55.880
the day to day work that people are doing with their heads down just trying to get something done. I think that that's definitely valuable as well, particularly
180
00:16:56.420 --> 00:16:56.920
as
181
00:16:57.380 --> 00:16:59.880
the language and the community grows and matures,
182
00:17:00.260 --> 00:17:06.315
and there are always new languages or new forms to capture people's attention and imagination.
183
00:17:06.695 --> 00:17:18.240
But I'm wondering what your thoughts are in terms of some of the forward looking efforts as far as maintaining the longevity and overall viability of the language in its community, particularly
184
00:17:18.860 --> 00:17:21.565
as we bring in new generations of developers
185
00:17:22.185 --> 00:17:34.680
who are growing up with the language as always having been there versus maybe the original generation that were escaping their original pain with more lower level languages or languages that didn't necessarily have the ergonomics of Python?
186
00:17:35.060 --> 00:17:43.835
Yeah. I I think there there are, a number of issues going forward that we as as a community, the PSF certainly will be,
187
00:17:44.554 --> 00:17:49.570
trying to be in in the in the lead on some of these things that we need to think about. And I think,
188
00:17:49.970 --> 00:17:50.470
particularly
189
00:17:51.090 --> 00:17:56.309
an issue that we will continue to work on and it will continue to be an issue is
190
00:17:57.085 --> 00:18:03.105
how to make an open source language and a community based around an open source language
191
00:18:03.565 --> 00:18:04.625
really sustainable.
192
00:18:05.340 --> 00:18:05.840
And
193
00:18:06.140 --> 00:18:07.760
that's in terms of both
194
00:18:08.299 --> 00:18:08.799
volunteers
195
00:18:09.100 --> 00:18:20.385
managing large community groups, but also in terms of the developers contributing to it. This is a hard problem that to my knowledge, nobody has really solved yet.
196
00:18:20.845 --> 00:18:21.345
But
197
00:18:22.460 --> 00:18:35.685
it is and it will continue to be an issue that in the case of something like Python, you have something that people are using in businesses to make a lot of money that is largely created by people who are giving their time. And that kind of asymmetry
198
00:18:36.305 --> 00:18:39.900
needs we need to have better solutions for that going forward.
199
00:18:40.680 --> 00:18:43.740
And no, I don't know what they are, but we need to figure that out.
200
00:18:44.040 --> 00:18:52.615
And so in addition to the work that you do with the PSF and for your day job and a number of other community activities and
201
00:18:52.915 --> 00:18:56.600
efforts that you're
involved with, You have also spent time
202
00:18:56.900 --> 00:19:04.200
working on writing the 2nd and third editions of the book, the quick Python book. So I'm wondering if you can start by giving a synopsis
203
00:19:04.565 --> 00:19:05.865
of what that book covers
204
00:19:06.245 --> 00:19:07.625
and some of the
205
00:19:07.925 --> 00:19:12.520
ideas behind who the target audience is. Yeah. This book
206
00:19:13.140 --> 00:19:20.520
is really aimed at people who already know how to code, but who are coming to Python from,
207
00:19:21.395 --> 00:19:22.695
some other language.
208
00:19:23.315 --> 00:19:33.870
So we're not really attempting to teach basic coding concepts. Instead, it's really aimed at being, if you know what you want to do, but you want to know how to do it in Python,
209
00:19:34.250 --> 00:19:36.269
then this is the book for you.
210
00:19:36.755 --> 00:19:37.255
So
211
00:19:37.795 --> 00:19:41.955
as such, it covers most of what I would say are the,
212
00:19:42.675 --> 00:19:43.175
intermediate
213
00:19:44.100 --> 00:19:47.000
to to moderately advanced features of the language.
214
00:19:47.460 --> 00:19:50.280
We don't spend much time on things like metaclasses.
215
00:19:51.765 --> 00:19:57.705
We haven't really it doesn't really go into the depths of asyncio or things like that. But instead,
216
00:19:58.005 --> 00:20:01.269
somebody who's coming in wanting to get in 1 place,
217
00:20:01.730 --> 00:20:15.775
kind of a quick grasp of the language as a whole so that they can go ahead and be productive in it. And given that you came in working on the 2nd edition, that leads me to assume that there was a first edition. So I'm wondering what the story is there as far as how you got involved,
218
00:20:16.179 --> 00:20:20.440
what the overall process was to update the book to the current state,
219
00:20:20.820 --> 00:20:34.610
and some of the, efforts that were involved as far as either trying to maintain the voice or adapt the voice to what something that you're familiar with and comfortable with writing in. The first edition was done in,
220
00:20:35.090 --> 00:20:35.590
1999
221
00:20:36.370 --> 00:20:37.910
for Python 1.52.
222
00:20:39.465 --> 00:20:39.965
And,
223
00:20:40.345 --> 00:20:41.805
the original authors
224
00:20:42.585 --> 00:20:43.085
had,
225
00:20:43.785 --> 00:20:46.365
after 10 years, it was 2, 008, 2009,
226
00:20:46.665 --> 00:20:55.790
they were looking at updating it because Python 3 was coming in and then, then Manning, the publishers felt that would be a a good time to do a major update.
227
00:20:56.435 --> 00:20:59.015
The original authors were not available
228
00:20:59.715 --> 00:21:00.455
or interested,
229
00:21:01.395 --> 00:21:02.455
in doing that.
230
00:21:02.755 --> 00:21:03.735
They had done
231
00:21:04.650 --> 00:21:06.110
really a pretty good job.
232
00:21:06.490 --> 00:21:11.549
The style that they used is sort of compatible with mine, which tends to be reasonably
233
00:21:12.169 --> 00:21:14.315
informal and kind of a straightforward,
234
00:21:14.855 --> 00:21:24.730
simple style. So, you know, the aim being readability, which is appropriate for a Python book, I guess. The the publishers weren't able to find anybody to do that book. And
235
00:21:25.990 --> 00:21:35.765
because of other various projects, I had a a literary agent who was in touch with them. So that's how I got in touch with Manning. And this was pitched as honestly
236
00:21:36.225 --> 00:21:48.995
a a fairly easy job. All you need to go do is go through and make sure that it's compatible with Python 3. Of course, going from Python 1 5 to to, 15 to to Python 3,
237
00:21:49.375 --> 00:21:52.275
turned out to be a major, major job.
238
00:21:52.655 --> 00:22:00.100
So it was it was probably on the order of doing a fresh book. There were certainly lots of things I left, but
239
00:22:00.720 --> 00:22:01.940
going that far,
240
00:22:02.320 --> 00:22:05.380
that was written before pep 8 was really a thing.
241
00:22:05.855 --> 00:22:08.275
There were all sorts of different coding styles.
242
00:22:08.975 --> 00:22:15.600
Practically every example in the in the book had something that really wasn't quite PEP 8 and needed to be fixed.
243
00:22:16.000 --> 00:22:17.539
We ended up actually
244
00:22:17.840 --> 00:22:33.225
removing the last few chapters because they covered things that were no longer applicable. I think there was something about Zope or something in it, which is fine. I started with Zope too, but that that's no longer an important platform that you would put in a in a book pitched at that level.
245
00:22:33.639 --> 00:22:34.139
So
246
00:22:34.600 --> 00:22:38.299
we basically had to do quite a lot of work. It ended up being
247
00:22:38.919 --> 00:22:40.539
a a pretty major rewrite.
248
00:22:40.975 --> 00:22:41.475
And
249
00:22:42.014 --> 00:22:52.389
I think fortunately, I started from a good place. But then the things that I added and the stuff that I wrote, I with the result, we got, I think, even better reviews for the 2nd edition.
250
00:22:52.850 --> 00:22:53.509
And then
251
00:22:54.130 --> 00:22:57.590
as we started talking about it a couple of years ago, it's like, well,
252
00:22:58.005 --> 00:22:59.865
might be time for another refresh.
253
00:23:00.804 --> 00:23:08.960
So that 1 was somewhat easier in terms of the language, but we also decided that given the way tech books go these days, we needed to add more,
254
00:23:09.419 --> 00:23:16.945
like, little quick check exercises so that people could confirm they'd gotten whatever was in the previous little section.
255
00:23:17.325 --> 00:23:20.144
And we also added some longer lab exercises
256
00:23:20.445 --> 00:23:30.639
at the end of each chapter so people could have a little bit more practical experience with the things covered. Cat it a case study at the end. So that ended up actually being
257
00:23:31.019 --> 00:23:31.760
a fairly
258
00:23:32.845 -->
00:23:39.585
extensive thing too. I think the lesson there is if a publisher tells you, don't worry. This is gonna be an easy job. Don't believe me.
259
00:23:40.830 --> 00:23:47.330
Basically, any anytime somebody says it's going to be easy, that usually means that they're just trying to get you on the hook and then
260
00:23:47.950 --> 00:23:52.315
you go All you need to do is our famous last words. Yes. Yes.
261
00:23:53.095 --> 00:23:58.955
And in at least the 3rd edition, I don't know if it was present in the 2nd edition, but the tail end of the book covers
262
00:23:59.450 --> 00:24:03.550
some introductory aspects of data analysis and data manipulation.
263
00:24:03.930 --> 00:24:04.750
So I'm wondering,
264
00:24:05.210 --> 00:24:14.434
if that is an artifact of the sort of current climate of Python and programming in general, or if that's something that you incorporated in that second edition
265
00:24:14.894 --> 00:24:19.180
as sort of, something that was starting to become important. No. The
266
00:24:21.080 --> 00:24:26.540
final chapters were more involved with kind of the beginnings of some web
267
00:24:26.865 --> 00:24:28.805
concepts for for web programming.
268
00:24:29.265 --> 00:24:31.845
And when we got to the 3rd edition,
269
00:24:32.225 --> 00:24:34.885
the climate had changed such that we felt,
270
00:24:35.410 --> 00:24:36.710
it was really,
271
00:24:37.650 --> 00:24:39.750
really important that we address
272
00:24:40.050 --> 00:24:41.190
some of the
273
00:24:41.490 --> 00:25:16.330
of the foundations that you need to use Python for data analysis. I, you know, it we we're not trying to be a data science book per se that that's, you know, many other books about that, But rather just now that you've been through the basics of Python, here's how you can kind of clean and normalize your data so that the data science can start. And that's that's kind of a reflection of the climate. And it's also sort of a reflection of the experience I've had over the years since even from the beginning, I've found that that's been 1 of the main things where, where Python has always saved me is when you need to
274
00:25:16.790 --> 00:25:22.625
do that whole ETL pipeline and and and get data ready for some use. It's been invaluable.
275
00:25:22.925 --> 00:25:31.120
Yeah. And even when you're using it for web development contexts, there's always data somewhere. There's always a need to be able to take in some source
276
00:25:31.420 --> 00:25:33.280
and be able to perform some manipulations
277
00:25:33.660 --> 00:25:51.295
on it and make it sane and usable somewhere else down the line, whether that's pulling from your database and sending it up to an API or receiving input from an API post request and putting it to the database, or as you said, building out a ETL pipelines or just systems management. It's always something that's useful no matter what domain you're working with.
278
00:25:51.695 --> 00:25:59.235
Absolutely. Yeah. And
in the overall process of writing the book and updating it, particularly going from that 1.5
279
00:25:59.535 --> 00:26:04.940
to 3 dot x, which is, as you said, a a big leap. I mean, people are having issues going from 2 to 3. So
280
00:26:06.200 --> 00:26:40.955
Right. But I'm wondering what you found to be some of the most interesting aspects of the language or the standard library that you were exposed to, just by virtue of having to dig deep into it that you either didn't really know about or didn't depreciate fully until having to go through that process? You know, I think partly doing something like this, I think partly coming from the perspective that I had, which is I knew the Python community and I knew that I guess to my mind, the worst thing that could happen would be to have these people that I knew ask me about things and I wouldn't know because I hadn't studied them, if you know what I mean. So
281
00:26:41.335 --> 00:26:43.755
I really just kind of almost over
282
00:26:44.135 --> 00:26:49.750
every aspect of the language. I think a couple of things that, that maybe stand out are
283
00:26:50.050 --> 00:26:54.870
kind of digging through the collections library to understand the pieces there.
284
00:26:55.170 --> 00:26:56.630
I'm not sure it's an underappreciated
285
00:26:57.010 --> 00:27:07.255
library, but it certainly is quite a piece of work that that people, like, I think should be aware of as they come into Python and the many things that it can do and the way that it does them Pythonically.
286
00:27:08.710 --> 00:27:15.210
And, you know, a little bit in terms of the ins and outs and and the many confusions of packaging
287
00:27:15.590 --> 00:27:16.090
and
288
00:27:16.845 --> 00:27:17.245
distributing,
289
00:27:17.805 --> 00:27:20.625
Python, things like that. I'm not sure I actually
290
00:27:21.245 --> 00:27:37.315
now know the answers to that, but I do know how complex the problem is and and several of the various attempts at solutions and things like that. So, so there, there are a lot of things that way. It really does as you work through all of that. And at some points it seems endless,
291
00:27:37.695 --> 00:27:47.370
but it it does actually give you a a pretty wide understanding, I think. And over the course of your career, I know that you've worked with a large variety of other languages
292
00:27:48.070 --> 00:27:57.125
and other language communities. So I'm wondering what have been some of the most useful lessons that you have learned both from those communities that you'd like to see brought back into
293
00:27:57.450 --> 00:27:58.350
the Python ecosystem
294
00:27:58.809 --> 00:28:13.145
or from those language implementations that you'd like to see in the Python language, and then in the reverse, things that you would like to see taken from Python and brought into some of these other ecosystems and languages? That strikes me as kind of a hard question because I have known
295
00:28:13.480 --> 00:28:20.700
lots of people who have coded in other languages, and I've coded in a number of languages over the years. But I'm not sure,
296
00:28:21.235 --> 00:28:24.615
particularly back in the day when I was was involved with those,
297
00:28:25.075 --> 00:28:29.815
that I ever really ran across anything like those communities.
298
00:28:30.159 --> 00:28:30.899
I think
299
00:28:31.440 --> 00:28:32.980
maybe the Linux community
300
00:28:33.600 --> 00:28:34.100
in
301
00:28:34.559 --> 00:28:36.340
the, you know, up to 2010
302
00:28:36.720 --> 00:28:44.164
or so would be about the last time I went to a Linux fest. But I think there there were some some interesting things about community.
303
00:28:44.945 --> 00:28:49.284
And otherwise for for the other languages, as I say, I never saw
304
00:28:49.640 --> 00:29:00.735
as much in the way of community. I mean, I guess I can recall being on c mailing lists back in the day, and the only thing that I seem to recall then are sort of people arguing a lot over
305
00:29:01.035 --> 00:29:08.110
how to format their code or things like that. It's probably unfair. But, you know, I I I guess I I don't really
306
00:29:08.490 --> 00:29:09.950
see that historically
307
00:29:10.250 --> 00:29:22.300
a lot of other languages have spent nearly the effort on that. Maybe in the past 10 years, they they have more so, but I I I don't think I can really comment very well on that. So,
308
00:29:23.320 --> 00:29:30.700
it's what all communities need to do in this day and age is continue to think about what makes them inclusive,
309
00:29:31.265 --> 00:29:36.085
how they can bring people in and make them feel welcome and and part of the community.
310
00:29:36.865 --> 00:29:40.690
And that can be across, you know, a wide number of axis.
311
00:29:41.070 --> 00:29:46.450
Gender is popularly mentioned but there are all sorts of other ways too where people feel not included
312
00:29:46.830 --> 00:30:09.915
and communities that don't deal with that I think do not have as strong a future as communities who do find a way to deal with that. So that's that's the thing I think and I I think the Python community has certainly tried hard to work on that. We have not always been successful, but we continue to try. And I think that is 1 of our strengths. And so beyond your work with the PSF
313
00:30:10.375 --> 00:30:17.590
and on the quick Python book and your day to day work of leading a technical team. What are some of the other projects
314
00:30:18.130 --> 00:30:23.030
that you have been involved with that you're most proud of, either technical or otherwise?
315
00:30:24.135 --> 00:30:25.275
Well, so
316
00:30:25.735 --> 00:30:26.875
I think it was
317
00:30:27.175 --> 00:30:27.675
in
318
00:30:28.455 --> 00:30:30.690
2, 006, 2, 000 and 7.
319
00:30:30.990 --> 00:30:33.970
I actually organized a bunch of educators
320
00:30:34.509 --> 00:30:39.649
to we created a number of improvements and patches for the turtle library.
321
00:30:40.255 --> 00:30:43.795
So we actually had all of our patches in Python 2.5's
322
00:30:44.175 --> 00:30:49.530
turtle library, I think it was. Sadly, well, not sadly, it was actually an improvement.
323
00:30:49.990 --> 00:30:57.024
In the next version of Python, they used Gregor Lingle's X turtle library, which did many more things much more nicely,
324
00:30:57.404 --> 00:31:03.510
and that's the current turtle library. But it was actually my first kind of contribution to the language.
325
00:31:04.130 --> 00:31:09.875
And of course, it involved bringing together a number of different ideas and getting them in it ready to go. So,
326
00:31:10.815 --> 00:31:16.355
so I was very proud of that at the time. I've done a number of things with adding events to PyCon.
327
00:31:16.900 --> 00:31:18.520
So most recently,
328
00:31:19.620 --> 00:31:20.120
I,
329
00:31:20.500 --> 00:31:22.120
was involved am involved
330
00:31:22.420 --> 00:31:27.215
with the hatchery program, which is a way that you can start new events at PyCon.
331
00:31:28.235 --> 00:31:40.590
And, the first event, the 1 that really was my motivation for for working with people to get this mechanism started, was the picon charles, the Spanish language track. So,
332
00:31:40.970 --> 00:31:42.750
I have I have been
333
00:31:43.050 --> 00:31:49.705
very, very happy to see, Last year, we had the 1st track of talks ever at PyCon US in Spanish,
334
00:31:50.085 --> 00:31:50.585
and,
335
00:31:51.284 --> 00:31:54.140
people were very excited about that. It's always very
336
00:31:54.760 --> 00:31:56.700
gratifying to be able to give
337
00:31:57.000 --> 00:31:59.580
people a voice that they didn't have before.
338
00:32:00.200 --> 00:32:00.679
So,
339
00:32:01.080 --> 00:32:05.625
that will continue again this year, and I'm I'm very excited to see that happen.
340
00:32:05.925 --> 00:32:09.385
And looking forward, what are some of the other projects
341
00:32:09.809 --> 00:32:10.390
or trends
342
00:32:11.170 --> 00:32:13.510
in the Python community and ecosystem
343
00:32:13.890 --> 00:32:19.025
or in technology as a whole that you are most excited about either just
344
00:32:19.345 --> 00:32:24.725
witnessing or participating in in the near to medium future? That's an interesting question.
345
00:32:25.345 --> 00:32:31.220
I think the 1 thing that I am most interested in watching develop technically,
346
00:32:31.520 --> 00:32:33.539
certainly in Python, is
347
00:32:34.080 --> 00:32:37.595
what sort of answers we come up with for
348
00:32:38.135 --> 00:32:42.555
basically the problem of the GIL and getting multi threaded performance
349
00:32:43.255 --> 00:32:47.970
improved so that we don't have problems with threading that we have right now.
350
00:32:48.270 --> 00:32:49.010
That is
351
00:32:49.310 --> 00:33:02.950
a really tough technical problem. I am not counting on having an explanation or an an an answer for that, but it's a problem I followed for some time. And I I
think that would be a very interesting development
352
00:33:03.490 --> 00:33:21.320
because I think the pressure for coming up with an answer for that continues to grow. So I have confidence that our community will find an answer and I'm really looking forward to seeing what trick we use to to get around that. Yeah. That's definitely 1 of the ones that comes up most often when I'm talking to somebody who is
353
00:33:21.700 --> 00:33:29.705
not directly involved in Python, but is sort of viewing it as a bystander and possibly working in a a different language environment, whether it's compiled
354
00:33:30.005 --> 00:33:30.825
or something,
355
00:33:31.205 --> 00:33:48.865
that natively supports multiprocess or multithreading of, oh, that's the language with the GIL. Right? Why would you wanna use that? It's Right. Right. Right. So yeah. Well, it's not that bad, but it's, yes, it is an issue. And and, it's have having followed the discussions and some of the problems,
356
00:33:49.165 --> 00:33:54.850
it it's a tough 1, but I still think somebody will crack it. And I'm just I'm really interested to see
357
00:33:55.150 --> 00:33:58.850
what course that will take. And are there any other aspects
358
00:33:59.230 --> 00:34:09.990
of the PSF or the quick Python book or your overall career and involvement with the Python language and community that you'd like to discuss further before we close out the show? I
359
00:34:10.450 --> 00:34:13.250
think I I'll throw in 1 last thing, which is that,
360
00:34:13.570 --> 00:34:17.590
a few weeks ago, I gave my first Python talk in Spanish.
361
00:34:18.015 --> 00:34:26.390
And so this has actually been, you know, whatever you want to to to include of this is fine. But this has actually been,
362
00:34:26.790 --> 00:34:30.730
something that I've been spending a lot of time on is the human language
363
00:34:31.270 --> 00:34:43.049
side of things. And I found that very interesting in that giving a talk in another language is really hard and yet all of those of us who speak English expect everybody else to do it all the time without understanding
364
00:34:43.430 --> 00:34:45.609
that. So I'm real interested
365
00:34:45.990 --> 00:34:47.450
in the development
366
00:34:47.750 --> 00:34:48.250
of,
367
00:34:48.585 --> 00:34:57.645
you know, the international communities using Python and how we can help them both in English, maybe by by improving our documentation
368
00:34:58.010 --> 00:35:05.470
and things like that, and also support them as they develop communities using their native languages, whether that's Chinese or Spanish
369
00:35:05.795 --> 00:35:15.210
or Portuguese or anything else, Hindi. So, so that's been kind of an interest of mine for the past couple of years now. Yeah. It's always interesting seeing
370
00:35:15.589 --> 00:35:20.250
the sort of prevalence or dominance of English in technical communities
371
00:35:20.835 --> 00:35:29.730
because of the fact that a lot of early computer systems were only able to represent Latin characters and just the lasting legacy that that has provided
372
00:35:30.110 --> 00:35:32.369
and some of the ways that that's actually starting
373
00:35:32.990 --> 00:35:38.530
to evolve into languages that support Unicode natively that'll allow people to define
374
00:35:38.895 --> 00:35:43.715
new language systems that are more native to their spoken tongue,
375
00:35:44.495 --> 00:35:46.500
and also things like natural language processing,
376
00:35:48.420 --> 00:36:19.235
centric because of the corpora that are available to it and some of the ways that new techniques are evolving to make it easier to provide different textual analysis run times for being able to interpret these different natural languages and be able to evaluate and incorporate new cultures and new languages as a result. Right. Yeah. I I think there's there's a lot to be done there. Alright. Well, for anybody who wants to get in touch with you or follow along with the work that you're doing, I'll have you add your preferred contact information to the show notes. Also,
377
00:36:19.775 --> 00:36:37.655
for anybody who's interested, I believe that I'll be having a giveaway for a couple copies of your book from Manning, and there'll be a discount code as well. So I'll put that all in the show notes for details with anybody who's interested. Bravo. And with that, I'll move us into the picks. And this week, I'm going to choose the program Inkscape.
378
00:36:38.035 --> 00:36:38.775
It's a
379
00:36:39.075 --> 00:36:40.055
SVG editor.
380
00:36:40.355 --> 00:36:44.055
It's open source, you know, easily installed on Linux, but it's also multiplatform.
381
00:36:44.355 --> 00:36:57.415
And I've been using it for doing all the design work that I do for the podcasts. So it's pretty easy to get up and running with, been very useful for my own purposes. And so for anybody who's working with scalable vector graphics, definitely recommend that. And so with that, I'll pass it to you, Naomi.
382
00:36:57.955 --> 00:37:00.535
Do you have any picks this week? Yes. Well, I mean, my pick
383
00:37:03.200 --> 00:37:03.700
is,
384
00:37:04.400 --> 00:37:07.380
what I've found 1 of the more entertaining entertainment
385
00:37:07.839 --> 00:37:08.980
things this year,
386
00:37:09.520 --> 00:37:10.160
which is,
387
00:37:10.875 --> 00:37:11.535
on Netflix,
388
00:37:12.315 --> 00:37:19.440
a series La Casa de las Flores or House of Flowers. It's a send up of Mexican telenovelas,
389
00:37:20.700 --> 00:37:24.320
which are kind of like soap operas only more so. So
390
00:37:24.780 --> 00:37:29.875
as, as those things tend to be, this is, this is just great fun. The more ridiculous
391
00:37:30.255 --> 00:37:36.260
and and over the top it is, the more serious they play it, which is exactly what you need to do in a send up. So,
392
00:37:36.560 --> 00:37:46.474
and it's it comes with, you know, an English version and a subtitle version and a Spanish version. So it's it's pretty accessible, but I found that to be very entertaining.
393
00:37:46.775 --> 00:37:53.670
Alright. Well, thank you very much for taking the time today to share your experience as working with Python and its community
394
00:37:53.970 --> 00:38:03.815
and the efforts that you've gone through to, help provide educational materials to us. So thank you for that, and I hope you enjoy the rest of your day. Okay. Well, thank you. You too.