+1 to checking on geojson specifics.
Now Python 2.6 ships a version of simplejson in the stdlib as json, but this
version is prior to simplejson 2.0.1 [1].
I wonder if the escaping of slashes/unicode issue persist in the version
shipped with Python 2.6?
Perhaps adding a specific simplejson version to the setup script would be a
good idea?


[1]
http://bob.pythonmac.org/archives/2008/10/02/python-26-released-now-with-json/


Regards,
Matt

2009/1/5 Sean Gillies <[email protected]>

> I've just been alerted to problems with geojson's tests, in
> combination with simplejson 2.0.7, which no longer escapes slashes and
> doesn't return unicode objects unless the the data warrants. I propose
> that we simplify the loads/dumps tests, checking only geojson-specific
> items, and trusting simplejson to get the others right. Thoughts?
>
> Sean
>
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.gispython.org/mailman/listinfo/community
>



-- 
Cheers,
Matt
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community

Reply via email to