8 messages in net.launchpad.lists.openstackRe: [Openstack] setuptools-git| From | Sent On | Attachments |
|---|---|---|
| Monty Taylor | Jun 28, 2012 12:55 pm | |
| Alan Pevec | Jun 29, 2012 4:06 am | |
| Monty Taylor | Jun 29, 2012 10:19 am | |
| Joshua Harlow | Jun 29, 2012 10:29 am | |
| Monty Taylor | Jun 29, 2012 10:46 am | |
| Alan Pevec | Jun 29, 2012 10:48 am | |
| Monty Taylor | Jun 29, 2012 10:59 am | |
| Monty Taylor | Jun 29, 2012 11:00 am |
| Subject: | Re: [Openstack] setuptools-git | |
|---|---|---|
| From: | Monty Taylor (mord...@inaugust.com) | |
| Date: | Jun 29, 2012 11:00:26 am | |
| List: | net.launchpad.lists.openstack | |
On 06/29/2012 10:48 AM, Alan Pevec wrote:
On Fri, Jun 29, 2012 at 7:19 PM, Monty Taylor <mord...@inaugust.com> wrote:
We use pip-requires as part of building the virtualenvs. Once we start using it, setuptools-git is pretty much required for running setup.py, so many common actions in our workflow will require it.
It's a good question though - and I consider the current existence of it in pip-requires purely a convenience hack. We don't have a strong place in our infrastructure to indicate setup_requires entries. I'll work on that next.
test-requires is also used when building venv and until there are separate build-requires, seems to be a better place for deps such as this
Trouble is that openstack.common.setup.parse_requirements() parses pip-requires and puts everything there into egg-info, which should be only run-time deps.
I just put up another possibility for review before I read this - check it out and see what you think - we can also go test-requires if you like that better.
Monty
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : open...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp