this is indeed true:
http://pythonhosted.org/setuptools/merge-faq.html
https://pypi.python.org/pypi/setuptools/0.8#id88

The recent changes to distribute-setup.py really caused some breaking in our environment. Is there not a preferred way to install this from pypi instead of direct raw scripts? Linking to the direct script and not locking to a specific commit is what broke this for us in the first place.

From the FAQ linked by @jamesonjlee it looks like we could simply run a easy_install -U pip setuptools, or perhaps point get_pip.py at a specific tree/commit.

UPDATE: I forgot to mention, that despite the concern around get_pip.py, this pull request works great for me and fixes all errors I was having 👍

Also, the usage we have that would be a good test is to:

python_pip "supervisor" do
  action :upgrade
end

http://tickets.opscode.com/browse/COOK-3305

@jamesonjlee
Thanks for the link you sent me. It was really useful!

@gondoi
Thanks for testing my code and creating the ticket. But I still wonder what should be the best way.

👍

Also ran into this issue, and successfully using @ka2n fork in our production environment.

Hello @ka2n,

Thank you for the pull request. Before we can merge it, we need a contributor license agreement (CLA) on file for you. More information can be found on the following wiki page:

http://wiki.opscode.com/display/chef/How+to+Contribute

Thank you,
Joshua

Hello @jtimberman,
Sorry for the delay in response, I've signed CLA as my real name "Katsuma Ito".

Thank you.

@ka2n there are still a few places where you're basing the guard condition on the presence of easy_install, rather than the way @coderanger suggested. Could you please update the remaining ones? Thanks! 😄

@sethvargo I did not realize this. I'll fix it as soon as possible. Thanks!

Thanky, if you can't get to fixing it tonight I can just take care of it and do the release magics :-)

the remaining places is this?

remote_file "#{Chef::Config[:file_cache_path]}/ez_setup.py" do
  source node['python']['setuptools_script_url']
  mode "0644"
  not_if { ::File.exists?(ez_binary) }
end

@coderanger Thanks you. I just woke up 😮 I'll fix this, but could you tell me above?

Yep, same thing of you can use import setuptools as a check to see if we need to do the install. Then you can remove all the stuff related to ez_binary too, since it shouldn't be needed in general.

@coderanger, @sethvargo
Sorry to make you wait. I learned a lot. Thanks!

👍