On Wed, 2007-06-13 at 05:50 -0700, ZebZiggle wrote:
> Hi, I'm really stuck on a bug (decode exceptions on attempting to save
> utf-8 to postgres text fields) and suspect I'm going to need the
> unicode branch to solve it. But I have some questions:
> 
> 1. When is it likely that this branch will be merged with trunk?

A couple of weeks, maybe. The Oracle branch is going first and that's
probably blocking on me installing Oracle at home to test it during the
merge.

However, it's also a bit irrelevant on many levels, since the unicode
branch is synced with trunk about twice a week. So it's just like using
trunk.

> 
> 2. How would you rank the stability of this branch currently?

Excellent.

> 
> 3. I've read http://code.djangoproject.com/wiki/UnicodeBranch but are
> there any more docs/examples of the conversion process available.

Read the UnicodeBranch wiki page.

> 
> I'm getting close to production for my project and fear adopting this
> branch will be a major setback if it's not ready for prime time.

Have a look at the rest of the posts in this thread. Notice that all
reported bugs are relatively trivial and have been fixed very quickly.
Should give you a feeling for how likely there are to be huge
insurmountable problems.

Regards,
Malcolm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to