Robin Becker wrote:
> First off there may be a bunch of other C extensions involved including
> PIL, but I built them all against this beta. What should I do to refine
> the error? Do I start with trying to establish which of the tests is
> guilty or build from source in debug mode and attempt to f
Terry Reedy wrote:
.
> Your choice, of course, but if the import succeeded, I personally would
> have runAll verbosely print testfile names before running them and then do
> a binary or trinary search to pin down the offending statement.
good points and a good idea. I'll try and pin down fir
"Robin Becker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'm testing ReportLab against Python-2.5beta1 and am getting some kind of
> problem as below
No kidding;-).
Based on incomplete knowledge, I will try to make some helpful comments.
> ===
I'm testing ReportLab against Python-2.5beta1 and am getting some kind of
problem as below
===
C:\Python24\reportlab\test>\python25\python runAll.py
.C:\Python24\reportlab\test\test_docstrings.py:54: ImportWarning: Not importing
directory 'C:\py
