[chef-dev] Possible Bug in Python Pip Provider


Chronological Thread 
  • From: < >
  • To:
  • Subject: [chef-dev] Possible Bug in Python Pip Provider
  • Date: Fri, 15 Mar 2013 07:19:36 -0700 (PDT)

I think this might be a bug, but I wanted to be sure before I created a 
ticket.

I'm attempting to use the the pip provider to install a package. I've got
something like this:

python_pip "http://myinternal.repo/django/1.5/django-1.5.tar.gz" do
  action :install
  virtualenv virtualenv_path
  version "1.5"
end

This yields the following error "HTTP error 404 while getting
http://myinternal.repo/django/1.5/django-1.5.tar.gz==1.5";

Now according to COOK-2297 and
https://github.com/opscode-cookbooks/python/blob/master/providers/pip.rb#L134,
If my package name begins with an http as mine does then "==1.5" should *not*
get appended onto the URL. It appears that might not be working and I think 
its
because the name attribute is wrong.

The provider is saying new_resource.*name*.downcase.start_with, but the
resource seems to define the attribute as package_name
(https://github.com/opscode-cookbooks/python/blob/master/resources/pip.rb#L30)

Should name and package_name be interchangable, or should the provider logic 
on
L134 be updated to use package_name?



Archive powered by MHonArc 2.6.16.

§