graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #00244
Re: [Question #100045]: no module named storage
Question #100045 on Graphite changed:
https://answers.launchpad.net/graphite/+question/100045
Status: Needs information => Open
densone gave more information on the question:
ok. I think I figured out the issue. My RPM installs carbon's lib
directory under:
/usr/lib/Pythonx.x/site-packages/carbon/
See below:
Python 2.4.3 (#1, Jul 27 2009, 17:56:30)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-44)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from carbon.storage import Store
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: cannot import name Store <-- This still breaks
>>> from carbon.storage import * <--- This works.
>>> from graphite.storage import * <-- This does not work
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: No module named storage
>>>
>>>
>>>
I am wondering if you can give me an overview of how you think the libraries should be laid out. Since graphite is broken into 3 apps, building the RPMS have proven to be a little tougher.
Here is my layout:
/usr/local/graphite -- This is where the Django app lives.
/usr/local/bin/whisper* - This is where the whisper bin files live
/usr/local/carbon - This is where carbon lives.
/usr/lib/Python2.4.x/site-packages/carbon - This is where carbon lib dir lives
/usr/lib/Python2.4.x/site-packages/graphite is where the whisper libs live
Advice would be great.
thanks
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.