Use the version directly instead of piping

miketheman · miketheman · commit 69ee5f9e9d2d · 2016-01-20T10:08:01.000-05:00
Turns out the example shown was for `curl|python...`, not invoking
directly. So we can use the same version identifer as if we were using
`pip` command itself.
diff --git a/Berksfile.lock b/Berksfile.lock
@@ -15,7 +15,7 @@ GRAPH
   chef_handler (1.2.0)
   minitest-handler (1.5.0)
     chef_handler (>= 0.0.0)
-  python (1.4.10)
+  python (1.4.11)
     build-essential (>= 0.0.0)
     yum-epel (>= 0.0.0)
   python_test (0.1.0)
diff --git a/metadata.rb b/metadata.rb
@@ -4,7 +4,7 @@
 license           "Apache 2.0"
 description       "Installs Python, pip and virtualenv. Includes LWRPs for managing Python packages with `pip` and `virtualenv` isolated Python environments."
 # This is our fork's version. It does not correspond to the upstream's cookbook at all.
-version           "1.4.10"
+version           "1.4.11"
 
 depends           "build-essential"
 depends           "yum-epel"
diff --git a/recipes/pip.rb b/recipes/pip.rb
@@ -44,7 +44,7 @@
   # Command updated to only allow pip versions prior to 8.0.0
   # @see https://github.com/DataDog/devops/issues/4225
   command <<-EOF
-  #{node['python']['binary']} get-pip.py | #{node['python']['binary']} - 'pip<8'
+  #{node['python']['binary']} get-pip.py 'pip<8'
   EOF
   not_if { ::File.exists?(pip_binary) }
 end
