graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #01791
[Question #179669]: Why aren't dependencies automatically pulled in?
New question #179669 on Graphite:
https://answers.launchpad.net/graphite/+question/179669
The install instructions[0] specify that I need to download whisper, carbon and graphite-web separately, then manually install all the dependencies. This seems silly for a project as established as this one, particularly since there exists a requirements.txt[1] with all the appropriate information, ready to be used with pip.
Now, I would just use that, but I'm confused about how the source tree[2] gets converted into these tarballs. It looks like the carbon and whisper directories are fairly directly converted to their respective tarballs, and most of whatever's left becomes graphite-web. Okay, I guess that's what the MANIFEST.in files are for.
Now, it's been a while since I've used pip for much of anything, but I remembered it installing dependencies of a package automagically. So now we get to the meat of my question: why can't I just do a `pip install graphite-web` and have carbon, whisper, Django, etc. all pulled in and installed?
PS: Carbon isn't Python 2.4-compatible; it needs the 2.5-y syntax of yield.
[0]: http://readthedocs.org/docs/graphite/en/latest/install.html
[1]: http://bazaar.launchpad.net/~graphite-dev/graphite/main/view/head:/requirements.txt
[2]: http://bazaar.launchpad.net/~graphite-dev/graphite/main/files
--
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.