This is sort of a patch suggestion. It would be nice to make the graphite module into a package I think (for the reasons packages exist in the first place...)
I experimented by moving 'graphite.py' to '__init__.py', thereby turning the graphite/ directory into a package. I have had no problems at all, all import statements in the code worked correctly. This can also be done by just linking the names together (symbolic or hard link) if one wishes the graphite.py filename to be preserved.
Rather than modifying the CVS file structure, instructions for making the link could be just added to the installation instructions as a hint.
I also tried this with PIDDLE, but it crashed and burned (I may not have had the latest version though) unfortunately, so the package idea will break "symmetry", but that doesn't seem like a real problem.
Greg Ball
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is sort of a patch suggestion. It would be nice to make the graphite module into a package I think (for the reasons packages exist in the first place...)
I experimented by moving 'graphite.py' to '__init__.py', thereby turning the graphite/ directory into a package. I have had no problems at all, all import statements in the code worked correctly. This can also be done by just linking the names together (symbolic or hard link) if one wishes the graphite.py filename to be preserved.
Rather than modifying the CVS file structure, instructions for making the link could be just added to the installation instructions as a hint.
I also tried this with PIDDLE, but it crashed and burned (I may not have had the latest version though) unfortunately, so the package idea will break "symmetry", but that doesn't seem like a real problem.
Greg Ball