Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
IANAL either,
but I think it doesn’t even come into play as long as you are not going to distribute the other software as well. For example, if you just tell your users “you have to install pyRXP in order to use this” (maybe easier if you make that “reportlab”), I think the GPL does not apply to your own code.EDIT: While there is no problem with using the reportlab toolkit in this particular case, the above interpretation does not seem to be correct (see agf’s comments on this answer below, as well as his own answer)
Note that the reportlab toolkit (although it’s by the same company “ReportLab”) doesn’t necessarily use pyRXP. They are two different things, each with it’s own license.
Looking at reportlab’s source code, in
reportlab.lib.rparsexml, it seems that pyRXP is only imported if it is installed (separately, because it is not included), and it uses another xml parser if pyRXP is not available. (I guess this is their way of allowing pyRXP to be used, and still keeping reportlab under BSD license)But maybe you’d best ask on the reportlab mailing list…