Re: Proposal: deprecate and remove django.utils.simplejson

2008-12-26 Thread Adam Findley
On Sun, Nov 30, 2008 at 11:50 PM, alex.gay...@gmail.com wrote: > > I think Eric's proposal is dead on, it accomplishes the same task, but > does it without inducing any overhead, since once we assume 2.6 we > inherently assume json is included. So +1 on it as Eric has > suggested, -0 as it was o

Re: Proposal: deprecate and remove django.utils.simplejson

2008-12-01 Thread zvoase
I think a better approach would be to have django.utils.simplejson as a sort of alias package (which is easy using Python's introspection). What would happen is this: A user imports either django.utils.simplejson, or something from inside it. We look for the 'json' package on the path (Python 2.6

Re: Proposal: deprecate and remove django.utils.simplejson

2008-12-01 Thread David Cramer
I have nothing against removing it from the built-in libs, but as long as we look for the system's libraries first what's the big downside to keeping it? On Dec 1, 5:02 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Mon, Dec 1, 2008 at 4:21 PM, James Bennett <[EMAIL PROTECTED]> wrote:

Re: Proposal: deprecate and remove django.utils.simplejson

2008-12-01 Thread Russell Keith-Magee
On Mon, Dec 1, 2008 at 4:21 PM, James Bennett <[EMAIL PROTECTED]> wrote: > > On Mon, Dec 1, 2008 at 12:45 AM, Russell Keith-Magee > <[EMAIL PROTECTED]> wrote: > I guess the thing that's bugging me is that this mostly seems to come > down to historical inertia; we already have simplejson in Django,

Re: Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread alex.gay...@gmail.com
I think Eric's proposal is dead on, it accomplishes the same task, but does it without inducing any overhead, since once we assume 2.6 we inherently assume json is included. So +1 on it as Eric has suggested, -0 as it was originally proposed. Alex On Dec 1, 1:25 am, "[EMAIL PROTECTED]" <[EMAIL

Re: Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread flo...@gmail.com
On Nov 30, 9:51 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > * Django 1.1: JSON serialization looks for system json/simplejson >   first, fall back to django.utils.simplejson if not found and warn >   with PendingDeprecationWarning whenever django.utils.simplejson is >   used. > > * Django 1.2

Re: Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread James Bennett
On Mon, Dec 1, 2008 at 12:45 AM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > I have to say I agree with Malcolm. I don't believe we are currently > hampered in any real way by bundling an old version of the SimpleJSON > library, and it doesn't take that much effort to update the bundled > ver

Re: Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread Russell Keith-Magee
On Mon, Dec 1, 2008 at 3:03 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Sun, 2008-11-30 at 23:51 -0600, James Bennett wrote: >> Apologies for bringing this up past the 1.1 feature deadline, but >> since this isn't a feature perhaps it'll be OK :) >> >> Currently, Django bundles a copy

Re: Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread Malcolm Tredinnick
On Sun, 2008-11-30 at 23:51 -0600, James Bennett wrote: > Apologies for bringing this up past the 1.1 feature deadline, but > since this isn't a feature perhaps it'll be OK :) > > Currently, Django bundles a copy of simplejson[1], at > django.utils.simplejson. We use this solely in the serializa

Proposal: deprecate and remove django.utils.simplejson

2008-11-30 Thread James Bennett
Apologies for bringing this up past the 1.1 feature deadline, but since this isn't a feature perhaps it'll be OK :) Currently, Django bundles a copy of simplejson[1], at django.utils.simplejson. We use this solely in the serialization system to support dumping to and loading from JSON fixtures.