[reportlab-users] Install problem with Reportlab 2.0

Parsifal Herzog parsifal.herzog at gmail.com
Fri Oct 6 13:21:38 EDT 2006


On Friday 06 October 2006 05:23, Robin Becker wrote:
> here is a patched version of setup.py; can you try this with and
> without the additional arguments
>
> --rl_accel=0
> --rl_accel=1
>
> etc?
>
> There was a complete borkeness in the version checking had no .c on
> the filename :(

The new setup.py failed with:

[parz at lobsang reportlab]$ python setup.py build
Traceback (most recent call last):
  File "setup.py", line 279, in ?
    run()
  File "setup.py", line 193, in run
    RL_ACCEL = _find_rl_accel()
  File "setup.py", line 89, in _find_rl_accel
    _.sort(_cmp_rl_accel_dirs)
  File "setup.py", line 66, in _cmp_rl_accel_dirs
    return cmp(_rl_accel_dir_info(b),__rl_accel_dir_info(a))
NameError: global name '__rl_accel_dir_info' is not defined
[parz at lobsang reportlab]$


I changed line 66 to
    return cmp(_rl_accel_dir_info(b),_rl_accel_dir_info(a))

and the install finally succeeded.

Thanks for the quick response. BTW, IMHO, the setup.py script is awfully 
complicated, and makes a lot of guesses and assumptions: such code is 
very fragile, yet it is deployed untested, probably because of the 
difficulty for developers to obtain a clean install environment. Why 
not just deliver rl_accel with Reportlab (it is very small,) and save 
all that failure-prone and unreliable testing in setup.py?


Thanks,
Parzival


More information about the reportlab-users mailing list