[Zope] Different field conversion for lines and ulines : why?

Pascal Peregrina Pperegrina at Lastminute.com
Thu Jan 11 07:59:38 EST 2007


Done:
 Issue 2263 of  Zope Bugs, Features, and Patches Collector [ZC]

Thanks.

Pascal


> De : Andreas Jung <lists at zopyx.com>
> Répondre à : Andreas Jung <lists at zopyx.com>
> Date : Thu, 11 Jan 2007 12:15:49 +0100
> À : Pascal Peregrina <Pperegrina at Lastminute.com>, <zope at zope.org>
> Objet : Re: [Zope] Different field conversion for lines and ulines : why?
> 
> 
> 
> --On 11. Januar 2007 11:23:45 +0100 Pascal Peregrina
> <Pperegrina at Lastminute.com> wrote:
> 
>> Hi,
>> 
>> I would like to know why lines fields are not converted with the same
>> logic as ulines fields in Zpublisher.Converters.
>> 
>> lines uses splitlines() while ulines uses split('\n')
>> 
>> This gives different result:
>>>>> ''.splitlines()
>> []
>>>>> ''.split('\n')
>> ['']
>>>>> u''.splitlines()
>> []
>>>>> u''.split('\n')
>> [u'']
>> 
>> So, when creating an empty Zope property for example, ulines version value
>> will be (u'',) while lines version value will be ()
>> 
>> 
> 
> Put this into the bugtracker. If possible with unittests and patches :-)
> 
> -aj
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists - 
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )


More information about the Zope mailing list