I've always said that EuroPython is my favorite conference. Better talks, better people. This is me sucking up to you. Better locations. No offense Cleveland or Pittsburgh. But Basel?

Really? Like last night my colleague Liza got four of us to go swim in the river. Would you swim in the river in Cleveland? You'd have to get vaccinated first I think and maybe sign a legal waiver. EuroPython has been going on for 18 years. Before I tell my story about the first Python event, let's talk a little bit about EuroPython and its first event.

First, this is the who's older than Paul check. Raise your hand if you were at EuroPython 1 2002 in Charleroi. One, two, three. EuroPython 1, not EuroPython 2. Okay, maybe. All right, yeah. Yeah, anyone else?

Charleroi. How about that? So I've got a funny story about, well actually before that, EuroPython society puts in all the work to do this conference. All we have to do is show up

and complain. Raise your hand if you are a organizer for the society or the conference. Anyone from the conference or society here? All right, we'll give them a round of applause. So my funny story about the first EuroPython in Charleroi. I think like July 2002, June or July 2002.

And I was in the process of moving to Europe, moving to live in France for four years. And I went up to go meet Denis Frere, the organizer of the conference at his office.

Was it Ariadne? Was that the name of his company? Anybody know Denis? And he had two people working for him, one a Dutch Belgian and one a French Belgian. And they both knew the other language.

Godefroy knew Dutch, Jean Paul knew French, but they spoke to each other in English. And that was my indoctrination into the world of Europe. Okay, we're going to have a little bit of fun today. Thank you to the EuroPython society for mistakenly selecting my talk.

This is not so much a talk, this is a dialogue. We'll talk a little bit about the format, but your job is to have fun in this conference. So transport yourself back. It's November 1994. I used to, when I give this talk, I used to make the mistake of saying, what were you doing in 1994? And half the audience was waiting to be conceived.

So I stopped saying that. There was a Clinton in the White House. What happened? Did he just die? Has he been dead the whole time? He's waiting to be conceived. Yay. All right.

Let's see if it's full screen that kills it. It's November 1994. There's a Clinton in the

White House. This slide was a lot funnier in August 2016 when I first read it. Joke's on me. Number one movie of the year? I make no statements about the quality of American cinema.

And there was a way to order freaking books on the internet. You fired up NCSA Mosaic. You connected to maybe AOL. And you got HTML 3.2 in all of its nested table glory.

This might have been pre-tables. Amazon, done pretty well since then. And the Python community started. And what do we mean when we say the Python community started? It wasn't that Python started, but the community started because there was a workshop at the National

Institutes of Standards and Technology in Gaithersburg, Maryland, a windowless, bureaucratic, Stalinesque office building with room for 20 people. And we thought,

what are we going to do with all that space? And a number of people that were on the mailing list had a workshop in November of 1994. This talk is intended to be a conversation. It's a little bit unusual in this room. But my job is to entertain you. My job is not to inform you

because I don't do that very well. My job is just to make you laugh. Your job is to entertain me. Otherwise, I'll get bored and we'll wrap this up quickly. I gave this talk in 10 minutes with Barry at PyCon. I gave it in two and a half hours with the PyCharm team in St. Petersburg. That was a fun version because by the end,

I achieved speaker nirvana. Everybody was talking to each other in the last 30 minutes I watched. If you have something useful to say, something important and educational,

say it anyway. You don't have to go over to here. Just raise your hand, stand up and say something. It can be true. It can be false. That's not important in this talk. But it needs to be funny. I've done a few things. I have the best job in the world. I'm developer advocate at PyCharm. I should be paying them instead of them paying me. But I've been

in the room when some important things happened. Let's talk about life in Python before 1994. Raise your hand if you were using Python in 1994. Damn. All right.

Some of you may have read Guido's blog about the start of Python. He was on the ABC team at CWI in the Netherlands. That team got disbanded because none of the 20 users of the

lessons and he decided to make his own language and the secret to success was the internet started to exist. If the internet would have started to exist when ABC was created and they would have put an open source license on it, then we may be using ABC right now. But Guido had spent a couple of years working on Python and distributing it leading into the

year of 1994. This was the landscape then. You don't hear, it's interesting. Do you use the word scripting language anymore? It's not used as much. Back then, these were the big fish in the world of scripting languages.

Perl, the write once language, Tcltk, which probably a lot of you have never heard of, and then Python were lumped into this category of scripting language. And it was a pejorative,

it was a way for serious people to look down their nose at that silly little toy. Sure, you can write your thing in Python, but then the grown-ups will show up and we'll convert it to C++. That story obviously didn't last very long. Again, this talk is a thin excuse for telling a

bunch of stories. Funny story about that book cover. This was the first Python book. Guido participated in the writing of it and they needed some cover art. And my company had a graphic designer who didn't know anything about programming. And so they said, hey, can you get her to do a logo? I was like, sure. And I went over to Nancy, I was like, Nancy, what should the

logo be? And I'm like, I don't know, a snake and a can of spam and maybe some glasses that look like Guido. So I embarrassingly am responsible for that horrific book cover art.

Another little story about Perl, this is a Guido story, a number of years later, Guido was sitting at a dinner table with Larry Wall and Tom Christensen and some other people from the Perl language, some kind of cross-language summit. And someone wanted to needle Larry Wall, the creator of Perl, about Python's success and he made some derisive, knowing Guido's like right there,

made some derisive comment about Python's a toy that'll never last. A little story on how I got to that conference. 1992, I was a officer in the Navy getting paid to go shark fishing.

In 1985, the movie Top Gun came out, the Navy didn't realize five years later they would have 100,000 people trying to start flight school, so I got paid for shark fishing. And I was working for a guy who called himself the Navy Internet Manager, which was like, what the hell is that? And the guy sitting in the cubicle next to me ran the domain for Navy.mil.

And I leaned over and I was like, I did this. Hey Mike, can I have www.navy.mil? He's like, what's that? He's like, well it's going to be the next big thing after gopher.

So I started working on that and I needed a scripting language. And I knew programming if you think dbase is programming and clipper, so I knew programming. And I went to the bookstore and I was the computer section and I was looking through books

and I'd heard about Perl and everybody that was extending, this was pre-CGI, everybody was extending their web servers was using Perl. I got this book on Perl, I'm like, hmm, oh hell no. And then found out that Python had a downloadable printable tutorial that was genetically written

for Paul Everett. It was like Guido knew how to infect my brain in a very particular fashion. And I actually, yeah, I printed that and took my 286 laptop to go visit someone I was dating in France and went through the tutorial in her kitchen.

And she married me anyway. So I had been using Python for a while and there was talk on the mailing list about going to organize a workshop because Guido was going to be in town. And Guido was invited over by the secret unknown superhero of the world of Python,

Michael McLay at NIST, got Guido over on a guest researcher visa, had this workshop invited people in. At the workshop he met Barry and Roger and Jeremy, well no, just Barry and Roger from CNRI who would later employ Guido during the take-off

of Python. So Michael was really responsible for a number of things including making it all happen. So Guido arrives at this conference, meets the various people including his future employers. At that time the community, whatever that meant, the Python community was a mailing list.

And you got on the mailing, actually I should tell a funny story, I'm going to say this a lot, a funny story. Back in the 1993 time frame when we did www.navy.mil,

there was a web page at CERN with the web servers on the internet. And you got listed on the web by emailing Tim Berners-Lee. And so I was like,

hey Tim, could you link to my site? Love, Paul. And so we have one of the, you know, it's like 200 web, you could print the web at that time. And the same thing for the Python mailing list, Guido administered an Etsy aliases file and whenever someone wanted to join

the community he had to go edit that damn thing and do all the magic to make the mail server work. Guido knew that there was a successful Python community when he could hand that task over to somebody else. And then he has another funny story about that, he and Barry talk about they put in or someone put in the gateway to comp laying Python news group, which probably

means nothing to any of you. There was this thing called news groups. And despite the comp and the laying in the damn title of the news group, all the messages were about Monty Python.

So this is the beginning of kind of the Python community. This is Guido's first email to the Python mailing list. Tells a little bit about the Python mailing list, how to subscribe, send messages and stuff like that. Isn't that cute? Guido introducing you to the Python community.

The second message explains how comments work. Okay, you put a little indent things and then, you know, make sure it wraps correctly and that's how we talk to each other.

I was talking about the NNTP gateway, so this is a little explanation of that and mailing lists and things. Let's do a test. That arrow points to two different acronyms. Raise your hand if you know what POTS is. That is amazing. For the record,

less than 10% of the hands went up. Raise your hand if you know what UUCP stands for. What does it stand for? Raise your hand again.

Yes, UNIX to UNIX copy. All right, you get a free ticket to my next talk. This is my first email to the Python mailing list. Anybody that knows me from the, okay, this next one, I stopped asking this question like a decade ago. PyCon DE gave a keynote.

Asked the question, got the answer, filed away the lesson, never asked that question again. Raise your hand if you've ever heard of ZOPE. For the record, 100% of the hands went up.

Anybody that knows me from the ZOPE days will think that this is funny as shit. The very first thing I ever talk about is persisting Python objects. This was kind of going into

the workshop, coming out of the workshop, the milieu that we existed in. What was the industry like? Remember, ask questions, please. Funny stories. Just stand up and say something. The milieu that we existed in for scripting languages meant that 107% of the emails were asking us how do you compare to TCL, how do you compare to,

you know, TK or Perl or something like that. Raise your hand if you know what TCL stands for. That's a half-hearted hand raise. You want to take a chance at it? I think you're sort of

right. Tool command language. You said tool chain command language. I gave you credit for that. Tool command language. Raise your hand if you've ever written any TCL. Raise your hand if you've ever used TK enter in the standard library.

Okay, you've written TCL not knowing that you did. Raise your hand if you think TK enter looks good. So this was kind of the milieu that we existed in, and it still was framing us

and framing all of these languages kind of in the toy section. And then with the advent of Java, which is essentially a systems language, the grown-ups had a very powerful tool to beat us over the heads with.

I'll tell the Java story in just a second. But needless to say, a tool that can power Instagram and Dropbox is no longer a toy, right? In fact, okay, another funny story. I think this is a Guido story, maybe, or a Barry. Google. Raise your hand if you've

heard of Google. Just kidding. Google has some money, right? The joke at Google is there's this one computer in the corner that serves the ads that makes 99% of the money. So Google

has a team of 100 people making this product called Google Video. I'm sure all of you use this every day right now. But they use C++.

And some of the PayPal refugees, too, I believe, had this website called YouTube, which was kicking their ass and rolling out a feature a week that would take like six months of the 100 grown-ups over at Google. So Google just bought them and rebranded it.

But that idea of the grown-ups versus the toy language was very predominant at this time, as someone who had to sell Python. In fact, the original sin of Zope and its commercial application server that came before, I'll tell a funny story about that,

that came before that was we are intentionally hiding Python. You could go in a web browser, write stuff, and didn't know that you were doing Python. So is it okay if I tell a funny story? So it's like 1996, 97, 96 and 97, we were making our money by selling an application

server to the Navy, $20,000. Now, you may have remembered that a couple of years before that, I was in the Navy, running the website, and then I left the Navy and became a consultant to get paid. That's not corrupt. I just thought I would throw that in there.

And for $20,000, you got a three and a half inch floppy. That's like, it doesn't feel like $20,000. Let's put it on a CD. So we put it on a CD that was 99.9% empty.

I kind of fill that up a little bit. So let's take all the docs, and this next part of the story may or may not be true. Just pretend it is. gzip or zip at the time has some command line options. Maybe you know of them. Zip minus nine. What does that do? Extra strong compression. Makes your stuff smaller.

Just takes longer to run, but makes your stuff smaller. What does zip plus nine do? You know what it does? $20,000. You run that and then rerun it and rerun it,

you got $20,000. So again, coming out of the conference, we had a community, which meant that we needed to start thinking about things like the long-term, because we've been around for months at that point.

And there was a conversation, many of you may have heard this conversation about Guido getting hit by a bus. This email is the origin of it by Michael McLean, the unsung hero. And I think the feeling was kind of that if Guido got hit by a bus, Jim Fulton, who later

came to work with me, was going to be the benevolent dictator for life. But as a community, as you start growing, you have to start thinking about things like that. And I went to go visit Guido at Google like 10 years ago when he was on the App Engine team. I think it's 10 years ago. And even at that point, I gave him credit because he was

able to do something that just about every other open source project fails at. What happens when the founder starts to move away a little bit? He hadn't left, but others were starting to carry the load, and one could imagine at that point life after Guido.

So going into all this, Guido and Michael organized a workshop at NIST, a little bit less deluxe than this environment. These were some of the topics before the conference. Hey, this is what the

vast audience will talk about. Read through this list, see if you have one that is still an itch that you would like to see Python scratch. Some of these are pretty funny. Some of them are tragic and funny in a tragic empathetic kind of way.

A couple of them are funny for me. Item number 11, Michael McLay and I spent our time at the workshop. The only contribution I had at the workshop was to say, hey, you know, those doc strings could contain information. Of course, I wanted to put like a dict in there,

but later on that became a thing. But Michael McLay and I spent time talking about formalizing the world of Python, the community of Python, and if there is a point to this talk, this is it, which is don't do that. Way premature.

We wrote bylaws. How stupid. It's like a Monty Python skit. Way premature for that. Okay, so anyway, raise your hand if you have something on this list that you think is still a burning issue in the world of Python. Anybody got one? I've already gotten you,

so you here in the blue. Got a funny story about that, but I'll come back. Yes. So same one. Yep. Okay. Anybody else got one? All right.

The gooey thing. I got a funny story about that. Anybody got another one? Number four. Oh, all right. It's interesting because like the conferences at that time were called SPAM 1, SPAM 2. They weren't called PyCon. Like SPAM 3, SPAM 3 at Reston was when that community

and David Asher, I think, started to get organized a little bit. The numeric people, the scientific people and stuff like that. Anybody else got one they feel really strongly about? Somebody towards the back so you can yell out. All right. So funny story, which might lead to another funny story. No, same funny story. Okay. This one,

I never said in public. Barry tells a story that Netscape was looking around for a scripting language for the browser. Contact Aguido. Yeah. It's as

if millions of voices cried out at once and said HTML is an HTML language, white space isn't significant. We need either semicolons or braces. Think about it. Better yet, don't think

about it. Pictures from the first workshop. Top left. That's Guido in the middle. Isn't he so cute? Talking to Roger Massey and Barry. Robin Friedrich in the middle on the top

was doing Python at NASA, like real NASA. Space command thing NASA in 1994. Later had a pretty big role in the organization of the Python community. My man Jim Fulton on the top right,

not the bus driver, but perhaps the replacement. Bottom left. This is a picture of what Barry Warsaw looks like on the inside. And then me before I got married and learned you can spend more than $5 on a haircut. Yes. I spent years asking the question, what is Orange Bobin?

Raise your hand if you know what, say it again. Orange Bobin is. Anybody know what Orange Bobin is? All right. The Dutch people know. You can make up a story and people would

believe it. It's the Python secret underground. What was the conference like? It didn't feel like all that much, but it did feel like something. Hard to look back on something and subject the biases. How am I doing on time? I have no idea. Got 10 minutes? Lunch wasn't all that good

yesterday anyway, right? What was it like? It felt like something was happening, something important, but being so new at the game, we didn't really foresee even the coming five years,

much less the coming 20 years. After this workshop, what did things look like? A little bit endless discussions about where we stack up in the scripting language universe. There was a second workshop, Spam 2 at Menlo Park. Is that right? USGS Menlo Park.

Jim Fulton organized that one and the third one at Reston. This one was at a windowless government office building at USGS with metal chairs, and the attendees included a guy from Sun's set-top box programming language team.

Anybody know what that became? Java. Didn't have the word Java on it at the time. Also had two guys showing their Python implementation at the Stanford digital library

project. Anybody know the name of that? I'll give you a hint. You could Google it. Things got a little bit bigger, so we organized the predecessor of the Python Software Foundation

called the Python Software Activity. Guido was at CNRI at the time. CNRI was kind of the home of it. Lots of funny stories about that. By the way, if you want an infinity of funny stories, I'll be at the PyCharm booth and I can tell the stories that can't be recorded,

like this one. We started some formalisms, the predecessors of PEPs called special interest groups. I had the unique distinction of creating the first special interest group, the catalog sig later taken on by Andrew Kuchling, which went nowhere.

This is the other part about the embedded client. Guido at CNRI, Corporation for National Research Initiatives, was on a team doing mobile code in Python on the internet,

including a web browser written in Python and TKNer called Grail. Then there was a third workshop. This is the agenda for it. The special interest group

called the locator. This is also the workshop where I have a funny story that I was doing a CGI workshop. In the audience were Greg Stein and someone else from his company, eShop, who was using our software that put a CORBA thing into the NCSA web server

and talked CORBA over to a long-running Python processor who didn't pay the CGI startup costs. Six months later he sold that damn thing to Microsoft and it was Microsoft commerce server version one had Python inside of it. How about that? Oh, I'm on time, cool.

We're not yet at the best two words of any presentation in conclusion. We're not at that point yet. This is questions and answers. Please get up and ask some questions. I'll help you

by asking a question. In an attempt to pretend this is informative, what could you learn from the first workshop that started the community in Python 1994? In particular, Python in its first third had a reputation as being friendly, being really friendly. Others, not so much. A lot of the

online community is quite hostile. Why Python? Why friendly? Jim Fulton had a good explanation

of this. We did this talk as a keynote panel two or three pythons ago and he said, Python is friendly and human because Guido is friendly and human. Everyone agrees with that. It didn't have to be that way. It could have been toxic like some other cultures.

Why did Python succeed and its competitors fail? Because at that workshop we put together a highly detailed strategic plan, budget, marketing, resource allocation. Luck?

Randomness? It's a good question and the lack of an answer is instructive. If you are making the next Python, if you are making the next big thing, remember to just work hard, treat people

right and success will surely follow 1% of the time. Any actual questions? Yes, Samuel. You are loud enough and I'll repeat it. Mission accomplished.

To repeat the question, Samuel lauded my highly researched and detailed presentation and then went on to a question about where would you look today for a similar community.

I will cheat and say Python. Here's my point. In Python, I like the first third, second third, the last third. First third is what I'm talking about here. Second third was like the rise of Python, the glory years, the PSF getting organized and especially PyCon becoming a financial

engine to accomplish missions including the last third. Why do you think Python has gotten really big? I asked this at St. Petersburg. Why do you think it's really taken off in the last five years? We don't have time to do an audience survey. Thanks. So I'll tell you what you think.

Your first thought is data science, right? So you could call that the another thing. It's almost like another thing that has the same values and lack of toxicity and stuff like that.

The other thing, though, I would say is women. In the second or the third third of Python, women, underrepresented groups, maybe Python in Africa, are becoming a thing, and that wasn't accidental. In the second third, PyCon and the PSF had a strategy,

had a plan, Jessica McKellar, and made shit happen. So you can look in the world of Python to find two examples that answer your question. Good enough? All right. Thanks. Other questions. First, Marc Andre. Were you at EuroPython One in Charleroi?

You were an organizer of EuroPython One? Hell yeah. You do not learn your lesson, do you? Jesus Christ. All right. Another question. Another funny story. Anybody got anything? Yes.

I am not, okay, I stopped learning Python at 1.5.2, so I am not allowed to answer that. I am not saying it has all been downhill from there, but after that, it was all computer sciency and stuff. No. Funny story. I forgot to repeat the question,

what is my least favorite feature of Python? So Larry asked, said Python 1.6 is great. Funny story. Sole purpose of the 1.6 release. Larry knows this story. He was teeing one up for me. Python 1.6 and Python 2.0 came out at the exact same time. What was the difference?

Come see me in the booth. I will tell you. Anything else? All right. In conclusion, thank you for saying so long. In conclusion, I talked about the first third, second third,

last third of Python. And in the first third, there was a group of people, especially in the second third of people, third of Python. Group of heroes. Now we are in this third third of Python, and hopefully there will be a fourth third, thus breaking my metaphor.

In this third third of Python, who is going to be the next bad ass? Python continues to thrive because new people come in, they become volunteers at the year of Python conference. They become middle management at the year of Python conference, then they spread into working for Larry on the core language. Get involved, have fun, do the work

no one else wants to do, kick ass, become a Python bad ass. Thank you.