Ship current code as v0.9? beta 1?

[Eli Stevens (Gmail)]

IS there any concrete reason why the current codebase can't get packaged up and shipped as either v0.9.0 or v0.9b1 or whatever?  I don't really care what it's called, I just want access to the _replicator DB.

We're at the start of a dev cycle, so now's the perfect time for us to include a beta package and work through any issues that might surface.

Eli

[Dirkjan Ochtman]

Yes. Sorry, I'm a bit busy at the moment.

I'd like to release whatever we have by then soon after the CouchDB 1.3 release.

BTW, I have an almost-fully-passing Python 3(.2) branch hanging
around. Would anyone be interested in helping out with that? It would
be kind of cool to ship that with 0.9, though I definitely don't think
we should block on it.

Cheers,

Dirkjan

On Fri, Mar 22, 2013 at 2:57 PM, Sharon Snyder <sharon...@gmail.com> wrote:
> I too would like to see this updated. It's been a long time since the last
> release and a lot of patches seem to have been added. Unfortunately we have
> a policy of not deploying patches for use in our production systems, so I am
> stuck with the 0.8 version.
>
> Sharon

> --
> You received this message because you are subscribed to the Google Groups
> "CouchDB-Python" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to couchdb-pytho...@googlegroups.com.
> To post to this group, send email to couchdb...@googlegroups.com.
> Visit this group at http://groups.google.com/group/couchdb-python?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Alexander Shorin]

Hi Dirkjan.

I would like to help with it. Currently, I'm also a bit busy, but will
have next week free to handle stuff that was assign to me. May also
take Py3K problem with it.
--
,,,^..^,,,

[Dirkjan Ochtman]

It would be great if you can address your bugs before the release.
I'll try to see if I can publish my patch queue, then we can see if we
can get it into a shippable state for 0.9.

Cheers,

Dirkjan

[Steve Ross]

Is the bug fixed where you can't server.resource.put_json to  /_config ?

[Dirkjan Ochtman]

On Sun, Mar 24, 2013 at 8:08 PM, Steve Ross <nowh...@gmail.com> wrote:
> Is the bug fixed where you can't server.resource.put_json to /_config ?

I think so. It would be great if you can check out tip, check for
yourself, and report back!

Cheers,

Dirkjan

[Alexander Shorin]

Hi Steve.

It's fixed, but works a bit complex:

server.resource('_config', section).put_json(key, json.encode(value))

Probably it's better to hide this behind some dict-like proxy:

# get whole section
server.config[section]
# get specific key
server.config[section][key]
# set value
server.config[section][key] = value
# remove value
del server.config[section][key]

But, anyway, I think it worths for his own issue to track on(:


--
,,,^..^,,,

[Dirkjan Ochtman]

On Sun, Mar 24, 2013 at 1:57 PM, Alexander Shorin <kxe...@gmail.com> wrote:

> I would like to help with it. Currently, I'm also a bit busy, but will
> have next week free to handle stuff that was assign to me. May also
> take Py3K problem with it.

Hi Alexander,

Would you have a chunk of time to look at your issues soonish? It
would be nice to get a release out.

Cheers,

Dirkjan

[Alexander Shorin]

Hi Dirkjan,

Yes, I'll handle them today at evening.
--
,,,^..^,,,