new app dependencies open source library

mattmakai · mattmakai · commit b9d73c49ca10 · 2015-05-05T07:37:50.000-04:00
diff --git a/all.html b/all.html
@@ -4485,13 +4485,23 @@ <h2>Application dependency resources</h2>
   shows how to use shell aliases and postactivate virtualenvwrapper hooks to
   make life easier when using these tools.</p>
 </li>
+</ul>
+<h2>Open source app dependency projects</h2>
+<ul>
 <li>
 <p><a href="https://github.com/kennethreitz/autoenv">Autoenv</a> is a tool for activating
   environment variables stored in a .env file in your projects' home
   directories. Environment variables aren't managed by virtualenv and although
   virtualenvwrapper has some hooks for handling them, it's often easiest to
   use a shell script or .env file to set them in a development environment.</p>
 </li>
+<li>
+<p><a href="https://github.com/bndr/pipreqs">Pipreqs</a> searches through a project for
+  dependencies based on imports. It then generates a requirements.txt file
+  based on the libraries necessary to run those dependencies. Note though that
+  while this could come in handy with a legacy project, the version numbers
+  for those libraries will not be generated with the output.</p>
+</li>
 </ul>
 <h2>Application dependencies learning checklist</h2>
 <p><i class="fa fa-check-square-o"></i>
diff --git a/application-dependencies.html b/application-dependencies.html
@@ -168,13 +168,23 @@ <h2>Application dependency resources</h2>
   shows how to use shell aliases and postactivate virtualenvwrapper hooks to
   make life easier when using these tools.</p>
 </li>
+</ul>
+<h2>Open source app dependency projects</h2>
+<ul>
 <li>
 <p><a href="https://github.com/kennethreitz/autoenv">Autoenv</a> is a tool for activating
   environment variables stored in a .env file in your projects' home
   directories. Environment variables aren't managed by virtualenv and although
   virtualenvwrapper has some hooks for handling them, it's often easiest to
   use a shell script or .env file to set them in a development environment.</p>
 </li>
+<li>
+<p><a href="https://github.com/bndr/pipreqs">Pipreqs</a> searches through a project for
+  dependencies based on imports. It then generates a requirements.txt file
+  based on the libraries necessary to run those dependencies. Note though that
+  while this could come in handy with a legacy project, the version numbers
+  for those libraries will not be generated with the output.</p>
+</li>
 </ul>
 <h2>Application dependencies learning checklist</h2>
 <p><i class="fa fa-check-square-o"></i>
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-04T21:44:27Z</updated></feed>
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-05T07:37:38Z</updated></feed>
diff --git a/source/content/pages/07-web-app-deployment/09-app-dependencies.markdown b/source/content/pages/07-web-app-deployment/09-app-dependencies.markdown
@@ -143,12 +143,20 @@ further clarification.
   shows how to use shell aliases and postactivate virtualenvwrapper hooks to
   make life easier when using these tools.
 
+
+## Open source app dependency projects
 * [Autoenv](https://github.com/kennethreitz/autoenv) is a tool for activating
   environment variables stored in a .env file in your projects' home
   directories. Environment variables aren't managed by virtualenv and although
   virtualenvwrapper has some hooks for handling them, it's often easiest to
   use a shell script or .env file to set them in a development environment.
 
+* [Pipreqs](https://github.com/bndr/pipreqs) searches through a project for
+  dependencies based on imports. It then generates a requirements.txt file
+  based on the libraries necessary to run those dependencies. Note though that
+  while this could come in handy with a legacy project, the version numbers
+  for those libraries will not be generated with the output.
+
 
 ## Application dependencies learning checklist
 <i class="fa fa-check-square-o"></i>

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	`<?xml version="1.0" encoding="utf-8"?>`
`2`		`-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-04T21:44:27Z</updated></feed>`
	`2`	`+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-05T07:37:38Z</updated></feed>`