Another couple weeks have slipped by and I continue to be crazy-busy.
(But each week I'm busy for a different reason--so I continue to be
foolishly optimistic that I'll soon get a week with some free time.)
Anyway, I don't have time to read this thread through with the care it
deserves, but I tho
>
> It's great to see some interest in multiple db support again :-)
>
> Ben
>
> 2008/5/20 Nicola Larosa (tekNico) <[EMAIL PROTECTED]>:
>>
>> Daryl Spitzer wrote:
>> > If I don't, I see if I can at least make enough time to writ
Perhaps bedros meant to ask if anyone is working on support in Django
for any "document based" databases.
strokeDB looks (to my untrained eye) similar to CouchDB. You'll find
plenty to read if you do a search for "couchdb django".
--
Daryl
On Tue, May 20, 2008 at 4:06 PM, Collin Grady <[EMAIL
I've unfortunately been too busy to make time to work on this since
PyCon. The last thing I've done (after writing some code on the
flight home) is to send a patch to Ben Ford. Not long after that Ben
created a Mercurial repository (with my patch) and a Trac project.
You'll want to contact him.
Ah. I'm glad I brought it up.
When the time comes to port my code, I'll try skipping step 1 first.
--
Daryl
On Fri, Mar 28, 2008 at 5:48 PM, Martin v. Löwis
<[EMAIL PROTECTED]> wrote:
>
> > I think you misunderstand the role of 2.6. See the seven steps under
> > "The recommended developm
-
Daryl
On Fri, Mar 28, 2008 at 12:32 PM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
>
> On Fri, Mar 28, 2008 at 8:07 PM, Daryl Spitzer <[EMAIL PROTECTED]> wrote:
> > On Fri, Mar 28, 2008 at 8:57 AM, Jacob Kaplan-Moss
>
> > > Ahh -- this was the part I was
On Fri, Mar 28, 2008 at 8:57 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> On Thu, Mar 27, 2008 at 5:10 PM, Martin v. Löwis
> <[EMAIL PROTECTED]> wrote:
> > So leave the code as-is, and have 2to3 fix it at installation
> > time (whenever setup.py is invoked by 3.x; setup.py itself
> >
Jacob writes:
> It's hard enough maintaining 2.3, 2.4, and 2.5 side-by-side...
Do you maintain them side-by-side, or do you just reject patches that
require new features introduced in 2.4 and 2.5? (I just assumed that
you maintain 2.3 compatibility by testing on 2.3.)
--
Daryl
On Thu, Mar 27
