pin requirements with `pip freeze`
authorM. Taylor Saotome-Westlake <ultimatelyuntruethought@gmail.com>
Tue, 6 Sep 2016 02:25:08 +0000 (19:25 -0700)
committerM. Taylor Saotome-Westlake <ultimatelyuntruethought@gmail.com>
Tue, 6 Sep 2016 02:25:08 +0000 (19:25 -0700)
I mean, I think there's a strong case that redirecting `pip freeze` to a
file pins too much (by printing everything in your virtualenv, not just
your first-order dependencies; in contrast, Cargo, Bundler, &c. are
smart enough to distinguish), but it's better than not having any idea
what software was used to make the site.

requirements.txt [new file with mode: 0644]

diff --git a/requirements.txt b/requirements.txt
new file mode 100644 (file)
index 0000000..81fdf0d
--- /dev/null
@@ -0,0 +1,12 @@
+blinker==1.4
+docutils==0.12
+feedgenerator==1.8
+Jinja2==2.8
+Markdown==2.6.6
+MarkupSafe==0.23
+pelican==3.6.3
+Pygments==2.1.3
+python-dateutil==2.5.3
+pytz==2016.6.1
+six==1.10.0
+Unidecode==0.4.19