On Tue, Mar 16, 2010 at 10:51:47PM +0700, Seksan Poltree wrote:
> Due to python2.6 have its own json implementation
> which might conflict with this package when import.
> I just simply include json-py in the extralib to avoid this.
> 
> The patch is attached.

While upstream code structure seems to be already set up to use, if
available, jsonpy, including its sources in w3af is not particularly
nice. In Debian we prefer to factor out common code of external
libraries for a lot of reasons (e.g. having a single package to fix in
case of security problems).

I doubt anybody would be happy to go forward with this patch without an
explicit agreement of the maintainer, hence I'm copying him (hi,
Luciano!) to explicitly ask for his advice.  As an alternative, instead
of explicitly including jsonpy in a diff, we might consider packaging a
new SVN snapshot which seems to contain jsonpy in it already (I've no
idea of the current status of SVN trunk, though).

Cheers.

PS Luciano, this is also an offer for help, if you approve the proposed
   patch, I'd be happy to contribute an NMU of this.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime

Attachment: signature.asc
Description: Digital signature

Reply via email to