Re: [dev] RFC: Transaction meta data
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-Fie6dYyVxa4T5aqr=pR3Q_zDaeDRMNUzKrk3=jeHw=JjQ@mail.gmail.com> |
On Thu, Mar 9, 2017 at 1:00 PM, David Glick (Glick Software) < [email protected]> wrote: > On 3/9/17 9:58 AM, Jim Fulton wrote: > > > > On Tue, Nov 15, 2016 at 1:25 PM, Jim Fulton <[email protected]> wrote: > >> tl;dr We've decided: >> >> - Transaction user and description are text (unicode) and it should >> be an error to try to set/update them with bytes, even if the bytes only >> contain ascii data, >> >> > Well, that turned out to be a bad idea, at least in the short run. > > It resulted in lots of projects being unable to use the current release of > the transaction package and unable to use current versions of dependent > projects, like ZODB, that depend on the transaction package. > > I propose to change the transaction to accept bytes for meta data. When > getting bytes, it will: > > - Issue a deprecation warning, and > > - decode the data assuming latin-1. > > Any objections? > > > Can you make the default encoding configurable? Plone uses utf-8 > consistently. > I can, but I'd *really* rather not. Does it make more sense to configure an encoding ot to fix the software? Would utf-8 be a better default? utf-8 with fallback to latin-1? Jim -- Jim Fulton http://jimfulton.info -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.