On 2011-04-16, at 16:52 , Antoine Pitrou wrote: > Le samedi 16 avril 2011 à 16:42 +0200, Dirkjan Ochtman a écrit : >> On Sat, Apr 16, 2011 at 16:19, Antoine Pitrou <solip...@pitrou.net> wrote: >>> What you're proposing doesn't address the question of who is going to >>> do the ongoing maintenance. Bob apparently isn't interested in >>> maintaining stdlib code, and python-dev members aren't interested in >>> maintaining simplejson (assuming it would be at all possible). Since >>> both groups of people want to work on separate codebases, I don't see >>> how sharing a single codebase would be possible. >> >> From reading this thread, it seems to me like the proposal is that Bob >> maintains a simplejson for both 2.x and 3.x and that the current >> stdlib json is replaced by a (trivially changed) version of >> simplejson. > > The thing is, we want to bring our own changes to the json module and > its tests (and have already done so, although some have been backported > to simplejson).
Depending on what those changes are, would it not be possible to apply the vast majority of them to simplejson itself? Furthermore, now that python uses Mercurial, it should be possible (or even easy) to use a versioned queue (via MQ) for the trivial adaptation, and the temporary alterations (things which will likely be merged back into simplejson but are not yet, stuff like that) should it not? _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
