[reportlab-users] More 2.2 questions - package rearrangement

[Andy Robinson]

I would like peoples' opinions on a package rearrangement.  This
should make it a bit easier to build standard distutils outputs and be
more in line with what other, younger Python packages do.

When we first started in 2000, the top-level directory in our CVS rep
WAS the 'reportlab' package, and we added all our docs, tests and
demos underneath it.  This also made distutils harder to use, as the
setup.py was under 'reportlab' rather than above it, which used to
confuse distutils.  Now we're in SVN, it's easy to rearrange things a
little.   The suggestion is that the >=2.2 source, when checked out or
downloaded as a .tar.gz, might contain the more conventional layout
like this....


- README, CHANGES etc
- setup.py
- reportlab/    - the pure python package
- reportlab/fonts/ - has more fonts added

- rl_addons/   - contains all C source code
     rl_accel/
     renderPM/

- docs/  - code for userguide etc, moved up out of the Python package
- tests/ - ditto
- demos/ - ditto

Setup.py can be written in such a way that it would build and install
the extensions if it could; but if not, it would print a message then
continue, just installing the pure python code.  So a "mininal"
Python-only distro is achieved by leaving out the rl_addons directory.

---

Does this change look worthwhile?  Would it help anyone or hinder
anyone, or are people indifferent?


Best Regards,

-- 
Andy Robinson
CEO/Chief Architect
ReportLab Europe Ltd.
165 The Broadway, Wimbledon, London SW19 1NE, UK
Tel +44-20-8544-8049