Merge pull request mikeckennedy#234 from talkpython/master

sync back MANY fixes and updates.

Author: mikeckennedy

transcripts/002_jesse_davis_talk_python_to_me_64.txt

@@ -698,7 +698,7 @@
 
 00:30:05 So you start making that error as well.
 
-00:30:06 Yeah, you're sort of PEP8 compliant straight away.
+00:30:06 Yeah, you're sort of PEP 8 compliant straight away.
 
 00:30:09 Exactly.
 

transcripts/002_jesse_davis_talk_python_to_me_64.vtt

@@ -1246,7 +1246,7 @@ It also shows you your unused imports and it checks your style while you go.
 So you start making that error as well.
 
 00:30:06.900 --> 00:30:09.540
-Yeah, you're sort of PEP8 compliant straight away.
+Yeah, you're sort of PEP 8 compliant straight away.
 
 00:30:09.540 --> 00:30:10.880
 Exactly.

transcripts/012_Deep_dive_into_Modules_and_Packages.txt

@@ -646,19 +646,19 @@
 
 00:17:47 one thing that I thought was interesting that you spoke about the tutorial was that
 
-00:17:52 structure guidelines, the PEP8 guidelines sometimes make your code more brittle in packages
+00:17:52 structure guidelines, the PEP 8 guidelines sometimes make your code more brittle in packages
 
 00:17:57 than otherwise should be.
 
 00:17:58 Oh yeah.
 
 00:18:01 Yes.
 
-00:18:01 One of the things with PEP8, I think is it predates some of the work that went on in
+00:18:01 One of the things with PEP 8, I think is it predates some of the work that went on in
 
 00:18:06 packages.
 
-00:18:07 I mean, you know, like, like PEP8 sort of talks that you should, you know, well, it
+00:18:07 I mean, you know, like, like PEP 8 sort of talks that you should, you know, well, it
 
 00:18:11 sort of says things like, oh, you should just do like an absolute import from kind of a top
 
@@ -776,21 +776,21 @@
 
 00:20:24 I think it's, I think it's really good advice.
 
-00:20:26 I propose we amend PEP8 to have the package relative imports.
+00:20:26 I propose we amend PEP 8 to have the package relative imports.
 
-00:20:31 I wonder when that part was written in PEP8.
+00:20:31 I wonder when that part was written in PEP 8.
 
 00:20:34 I mean, it's, I have to, I hate to admit this on like a podcast, but I'm sort of a flagrant
 
-00:20:40 PEP8 violator.
+00:20:40 PEP 8 violator.
 
 00:20:42 Don't worry, you, nobody can see the code, so they won't really know about it.
 
 00:20:45 It's fine.
 
 00:20:46 Yeah.
 
-00:20:46 It's, I, I, I don't mean to violate it, but I think it's, you know, PEP8 comes after
+00:20:46 It's, I, I, I don't mean to violate it, but I think it's, you know, PEP 8 comes after
 
 00:20:53 the point at which I got involved with Python.
 

transcripts/012_Deep_dive_into_Modules_and_Packages.vtt

@@ -988,7 +988,7 @@ Nice.
 Uh, one thing that I thought was interesting that you spoke about the tutorial was that
 
 00:17:52.240 --> 00:17:57.700
-structure guidelines, the PEP8 guidelines sometimes make your code more brittle in packages
+structure guidelines, the PEP 8 guidelines sometimes make your code more brittle in packages
 
 00:17:57.700 --> 00:17:58.860
 than otherwise should be.
@@ -1000,13 +1000,13 @@ Oh yeah.
 Yes.
 
 00:18:01.780 --> 00:18:06.900
-One of the things with PEP8, I think is it predates some of the work that went on in
+One of the things with PEP 8, I think is it predates some of the work that went on in
 
 00:18:06.900 --> 00:18:07.380
 packages.
 
 00:18:07.380 --> 00:18:11.660
-I mean, you know, like, like PEP8 sort of talks that you should, you know, well, it
+I mean, you know, like, like PEP 8 sort of talks that you should, you know, well, it
 
 00:18:11.660 --> 00:18:16.620
 sort of says things like, oh, you should just do like an absolute import from kind of a top
@@ -1183,16 +1183,16 @@ Yeah.
 I think it's, I think it's really good advice.
 
 00:20:26.180 --> 00:20:31.220
-I propose we amend PEP8 to have the package relative imports.
+I propose we amend PEP 8 to have the package relative imports.
 
 00:20:31.220 --> 00:20:34.280
-I wonder when that part was written in PEP8.
+I wonder when that part was written in PEP 8.
 
 00:20:34.280 --> 00:20:40.140
 I mean, it's, I have to, I hate to admit this on like a podcast, but I'm sort of a flagrant
 
 00:20:40.140 --> 00:20:41.480
-PEP8 violator.
+PEP 8 violator.
 
 00:20:42.660 --> 00:20:45.840
 Don't worry, you, nobody can see the code, so they won't really know about it.
@@ -1204,7 +1204,7 @@ It's fine.
 Yeah.
 
 00:20:46.500 --> 00:20:53.280
-It's, I, I, I don't mean to violate it, but I think it's, you know, PEP8 comes after
+It's, I, I, I don't mean to violate it, but I think it's, you know, PEP 8 comes after
 
 00:20:53.280 --> 00:20:55.900
 the point at which I got involved with Python.

transcripts/014_Converting_Patreon.com_to_Python_3.txt

@@ -1204,9 +1204,9 @@
 
 00:42:16 That seems like a really good idea.
 
-00:42:18 Did you do anything like PyFlakes or any of the sort of PEP8 type checking tools to see how people are doing there?
+00:42:18 Did you do anything like PyFlakes or any of the sort of PEP 8 type checking tools to see how people are doing there?
 
-00:42:27 We use, pretty extensively, we use PyCharm inside the company that does the PEP8 checking for us.
+00:42:27 We use, pretty extensively, we use PyCharm inside the company that does the PEP 8 checking for us.
 
 00:42:33 And it's actually, I usually did development, I mean, I've usually done development on just like Vim or Emacs,
 

transcripts/014_Converting_Patreon.com_to_Python_3.vtt

@@ -1813,10 +1813,10 @@ Yeah, that makes sense.
 That seems like a really good idea.
 
 00:42:18.820 --> 00:42:27.260
-Did you do anything like PyFlakes or any of the sort of PEP8 type checking tools to see how people are doing there?
+Did you do anything like PyFlakes or any of the sort of PEP 8 type checking tools to see how people are doing there?
 
 00:42:27.260 --> 00:42:33.340
-We use, pretty extensively, we use PyCharm inside the company that does the PEP8 checking for us.
+We use, pretty extensively, we use PyCharm inside the company that does the PEP 8 checking for us.
 
 00:42:33.340 --> 00:42:39.860
 And it's actually, I usually did development, I mean, I've usually done development on just like Vim or Emacs,

transcripts/018_quantifiedcode.txt

@@ -960,7 +960,7 @@
 
 00:34:57 And it actually prints out an ISBN number of a book that is mentioned in the movie.
 
-00:35:03 And he also ran it through our static analysis software and he found that actually it's not like PEP8 compliant and there's some other things in it.
+00:35:03 And he also ran it through our static analysis software and he found that actually it's not like PEP 8 compliant and there's some other things in it.
 
 00:35:09 So it probably shouldn't be security code, which it was in the movie.
 

transcripts/018_quantifiedcode.vtt

@@ -1444,7 +1444,7 @@ And he just wrote down the code because he was interested in what it would do.
 And it actually prints out an ISBN number of a book that is mentioned in the movie.
 
 00:35:03.320 --> 00:35:09.820
-And he also ran it through our static analysis software and he found that actually it's not like PEP8 compliant and there's some other things in it.
+And he also ran it through our static analysis software and he found that actually it's not like PEP 8 compliant and there's some other things in it.
 
 00:35:09.820 --> 00:35:13.620
 So it probably shouldn't be security code, which it was in the movie.

transcripts/022_cpython.txt

@@ -216,7 +216,7 @@
 
 00:07:43 And eventually your program runs.
 
-00:07:45 So we we don't do the parsing stage because I think parsing is fairly standard.
+00:07:45 So we don't do the parsing stage because I think parsing is fairly standard.
 
 00:07:50 And that's covered by most kind of introductory compilers classes.
 

transcripts/022_cpython.vtt

@@ -328,7 +328,7 @@ There's just a lot of C code behind the scenes that keeps track of a lot of stuf
 And eventually your program runs.
 
 00:07:45.820 --> 00:07:50.960
-So we we don't do the parsing stage because I think parsing is fairly standard.
+So we don't do the parsing stage because I think parsing is fairly standard.
 
 00:07:50.960 --> 00:07:54.860
 And that's covered by most kind of introductory compilers classes.