transcripts

Author: mikeckennedy

transcripts/002_jesse_davis_talk_python_to_me_64.txt

@@ -222,7 +222,7 @@
 
 00:13:15 So, you need a driver.
 
-00:13:16 And the standard driver for MongoDB is called PyMongo, and you install it from PyPI via PIP, install PyMongo.
+00:13:16 And the standard driver for MongoDB is called PyMongo, and you install it from PyPI via pip, install PyMongo.
 
 00:13:26 The current version is about to be 3.0, which we'll release in just about a week,
 

transcripts/002_jesse_davis_talk_python_to_me_64.vtt

@@ -379,7 +379,7 @@ So, you need a driver.
 And the standard driver for MongoDB is called PyMongo,
 
 00:13:21.980 --> 00:13:26.120
-and you install it from PyPI via PIP, install PyMongo.
+and you install it from PyPI via pip, install PyMongo.
 
 00:13:26.120 --> 00:13:32.120
 The current version is about to be 3.0,

transcripts/013_Flask_web_framework_and_much_much_more.txt

@@ -434,9 +434,9 @@
 
 00:12:57 So, like, how do I get started?
 
-00:12:59 So, I guess the easiest way to get started with it is to download it from PIP, which is what most people use now.
+00:12:59 So, I guess the easiest way to get started with it is to download it from pip, which is what most people use now.
 
-00:13:05 Set up a virtual env, get PIP, install Flask in there, and then you can probably even just go to the front page of Flask and copy-paste the Hello World example.
+00:13:05 Set up a virtual env, get pip, install Flask in there, and then you can probably even just go to the front page of Flask and copy-paste the Hello World example.
 
 00:13:15 And that's probably good enough to get going, which is really not that much.
 

transcripts/013_Flask_web_framework_and_much_much_more.vtt

@@ -679,10 +679,10 @@ I suspect many people out there have written Flask apps, but also many of them h
 So, like, how do I get started?
 
 00:12:59.080 --> 00:13:05.900
-So, I guess the easiest way to get started with it is to download it from PIP, which is what most people use now.
+So, I guess the easiest way to get started with it is to download it from pip, which is what most people use now.
 
 00:13:05.900 --> 00:13:15.740
-Set up a virtual env, get PIP, install Flask in there, and then you can probably even just go to the front page of Flask and copy-paste the Hello World example.
+Set up a virtual env, get pip, install Flask in there, and then you can probably even just go to the front page of Flask and copy-paste the Hello World example.
 
 00:13:15.740 --> 00:13:19.700
 And that's probably good enough to get going, which is really not that much.

transcripts/022_cpython.txt

@@ -1490,7 +1490,7 @@
 
 00:55:41 Because one of the annoying things about starting up with any kind of new language is just having to install extra packages.
 
-00:55:48 So for people who are a bit more savvy, they can use PyPy, Easy Install, PIP, those things.
+00:55:48 So for people who are a bit more savvy, they can use PyPy, Easy Install, pip, those things.
 
 00:55:53 But sometimes they get annoying because you try to install it and it says, oh, some dependency is not found.
 

transcripts/022_cpython.vtt

@@ -2242,7 +2242,7 @@ The reason why I suggest those is, especially for beginners, is because they hav
 Because one of the annoying things about starting up with any kind of new language is just having to install extra packages.
 
 00:55:48.060 --> 00:55:53.500
-So for people who are a bit more savvy, they can use PyPy, Easy Install, PIP, those things.
+So for people who are a bit more savvy, they can use PyPy, Easy Install, pip, those things.
 
 00:55:53.500 --> 00:55:57.540
 But sometimes they get annoying because you try to install it and it says, oh, some dependency is not found.

transcripts/023_3d_printing.txt

@@ -436,7 +436,7 @@
 
 00:13:06 So being in the same kind of stack that way helps a whole heck of a lot.
 
-00:13:10 Beyond Salt for like our sort of coordination of commands and our configuration management, we actually use PIP.
+00:13:10 Beyond Salt for like our sort of coordination of commands and our configuration management, we actually use pip.
 
 00:13:20 So when we push a new update to some service, and we have a lot of services, we try to run essentially a microservice architecture.
 
@@ -478,13 +478,13 @@
 
 00:14:32 And our deployment system just says, hey, I want you to pip install, upgrade, you know, this system for, say, managing 3D models.
 
-00:14:42 And it will look, find the newest update, install that update, download any dependencies, internal or external, get them all installed via PIP.
+00:14:42 And it will look, find the newest update, install that update, download any dependencies, internal or external, get them all installed via pip.
 
 00:14:49 And then it just tells MicroWSGI to bounce the process if need be so that it updates all of its logic.
 
 00:14:54 And off we go.
 
-00:14:56 Like, we're PIP.
+00:14:56 Like, we're pip.
 
 00:14:58 That's a really interesting way to do it.
 
@@ -546,7 +546,7 @@
 
 00:17:01 We struggled with version numbers, actually, since our version numbers in Git, our version numbers went all the way through from Git, tags, all that stuff, all the way through Jenkins.
 
-00:17:12 And Python 3, PIP, the latest stuff, is all very exacting about how it treats your version numbers.
+00:17:12 And Python 3, pip, the latest stuff, is all very exacting about how it treats your version numbers.
 
 00:17:19 And so we'll occasionally get internal conflicts or we accidentally push something to production that's not a production build because, oh, it turns out that the way our Git tag translated into a pip version ended up making it more recent than our last one on accident.
 

transcripts/023_3d_printing.vtt

@@ -661,7 +661,7 @@ And so everyone figures out how stuff gets deployed and they debug it.
 So being in the same kind of stack that way helps a whole heck of a lot.
 
 00:13:10.980 --> 00:13:18.700
-Beyond Salt for like our sort of coordination of commands and our configuration management, we actually use PIP.
+Beyond Salt for like our sort of coordination of commands and our configuration management, we actually use pip.
 
 00:13:20.360 --> 00:13:29.240
 So when we push a new update to some service, and we have a lot of services, we try to run essentially a microservice architecture.
@@ -724,7 +724,7 @@ They're just part of the dependencies.
 And our deployment system just says, hey, I want you to pip install, upgrade, you know, this system for, say, managing 3D models.
 
 00:14:42.560 --> 00:14:49.180
-And it will look, find the newest update, install that update, download any dependencies, internal or external, get them all installed via PIP.
+And it will look, find the newest update, install that update, download any dependencies, internal or external, get them all installed via pip.
 
 00:14:49.180 --> 00:14:54.480
 And then it just tells MicroWSGI to bounce the process if need be so that it updates all of its logic.
@@ -733,7 +733,7 @@ And then it just tells MicroWSGI to bounce the process if need be so that it upd
 And off we go.
 
 00:14:56.040 --> 00:14:58.040
-Like, we're PIP.
+Like, we're pip.
 
 00:14:58.040 --> 00:15:01.440
 That's a really interesting way to do it.
@@ -826,7 +826,7 @@ I mean, there's a few things that are a little bit difficult.
 We struggled with version numbers, actually, since our version numbers in Git, our version numbers went all the way through from Git, tags, all that stuff, all the way through Jenkins.
 
 00:17:12.960 --> 00:17:19.020
-And Python 3, PIP, the latest stuff, is all very exacting about how it treats your version numbers.
+And Python 3, pip, the latest stuff, is all very exacting about how it treats your version numbers.
 
 00:17:19.020 --> 00:17:33.320
 And so we'll occasionally get internal conflicts or we accidentally push something to production that's not a production build because, oh, it turns out that the way our Git tag translated into a pip version ended up making it more recent than our last one on accident.

transcripts/025_effective_python.txt

@@ -1444,7 +1444,7 @@
 
 00:45:29 You know, it really depends on your company.
 
-00:45:33 I think if you're comfortable with PIP, then yeah, it's pretty good, especially if you're
+00:45:33 I think if you're comfortable with pip, then yeah, it's pretty good, especially if you're
 
 00:45:37 doing deployments off of it.
 

transcripts/025_effective_python.vtt

@@ -2170,7 +2170,7 @@ Do you recommend having like an internal private package server?
 You know, it really depends on your company.
 
 00:45:33.840 --> 00:45:37.420
-I think if you're comfortable with PIP, then yeah, it's pretty good, especially if you're
+I think if you're comfortable with pip, then yeah, it's pretty good, especially if you're
 
 00:45:37.420 --> 00:45:38.460
 doing deployments off of it.