* Bernd Zeimetz , 2010-02-16, 23:25:
I start to wonder how they make a difference betweek py2.6's json and
python-json, if its necessary at all for anyjson.
It doesn't deal very well... Here's what happens in a clean chroot with
only python-anyjson and python-json installed:
import anyjson
Alexandre Quessy wrote:
> Hello everyone,
> It seems like python-json should either be renamed of deprecated.
>
> Meanwhile, all the Python application and modules that use JSON should
> be careful when importing the json module. Here's how I do it. (see the
> code extract below)
>
The other opti
Hello everyone,
It seems like python-json should either be renamed of deprecated.
Meanwhile, all the Python application and modules that use JSON should
be careful when importing the json module. Here's how I do it. (see the
code extract below)
# JSON im# JSON import:
try:
import json # pytho
On Feb 14, 2010, at 09:18 AM, Paul Wise wrote:
>Unless they can be convinced to undo that, python-json is clearly at a
Very unlikely that will happen.
-Barry
signature.asc
Description: PGP signature
So basically, Python upstream hijacked a part of the import namespace.
Unless they can be convinced to undo that, python-json is clearly at a
disadvantage and future JSON consuming Python code will likely use the
Python json module since it comes with Python. Therefore python-json
needs to be remov
There are currently two packages providing Python modules named 'json':
python2.6 and python-json. Unfortunately, those module are not
API-compatible.
Here is my brief analysis of reverse-dependencies of python-json:
- w3af-console depends on python-json and relies on its particular API.
That
6 matches
Mail list logo
