Conversation
Hi @sivy, First of all, I'd like to apologize that this has not received a reply after four months. That's pretty awful response time on our part. We're still catching up on the backlog of tickets that need to be handled in JIRA, and haven't gone through to catch up on pull requests or match them to the tickets. The COOK-1063 ticket is not in resolve status so we've not triaged it, it's not that we're ignoring you! We would like to merge this to add this feature for folks, but I do not see you on our contributor list. We do require a contributor license agreement for all our cookbooks to help protect the community from nefarious copyright entanglements (think SCO vs IBM debacle). Please see our page on how to contribute to Opscode open source projects. Finally, we have moved our cookbooks out to their own separate repositories under the "opscode-cookbooks" organization some time ago. May I trouble you to apply your patch to the new repository for the python cookbook? Thank you for contributing! |
Hi Josh - look under the company list for Wallrazer. that's me. :-) And yes, I'll submit a new patch to the new repo tomorrow. --Steve Steve (Gmail) On Thursday, June 21, 2012 at 9:59 PM, Joshua Timberman wrote:
|
Hi @sivy, Thank you for submitting a CLA/CCLA. I don't see a PR on the current python cookbook repo, and this PR has merge conflicts. Will you be able to submit a new PR there? Thanks! |
Hi Josh, I'll finally sit down now and fix up a patch on the proper repo. :-) --Steve Steve Ivy On Sunday, September 16, 2012 at 10:03 AM, Joshua Timberman wrote:
|
Awesome, thank you! |
Hoping I might convince you to submit that pull request. Here's a sailboat in hopes it might be the convincing factor. ⛵ ^_^ |
Fairly certain that is a schooner. ;) |
Ok ok, I give. I'll dig out the code in the am and see if I can mash mine into the current state if the python cookbook. :-) Steve Ivy - steve@wallrazer.com On Oct 14, 2012, at 10:12 PM, Joshua Timberman notifications@github.com wrote:
|
Teach python_pip about requirements files.
From the updated README:
I added some code to check for
pip --version
, as 1.1 removed the--environment
parameter that the python_pip resource currently uses for installing into a virtualenv.