-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:lines converter converting to list of bytes instead of list of str #638
Comments
seems to be related to #558 You could and possible should use And here is the pr which turned it into bytes - by consensus: Also, the documentation has to checked once again. The "convert to native strings" for "lines" is obviously wrong - unlike most of the others, especially "tokens" which really return a list of "native strings". I'd say this is an inconsistency. |
FWIW, my memory says |
You are possibly right...have to check this in our own enviroment |
Tres Seaver wrote at 2019-5-22 13:03 -0700:
FWIW, my memory says `ulines` was how you specified that you really wanted a sequence of text, rather than bytes.
Of course, for Python 3, the "u*" converters should behave identically
to the corresponding converters without the "u" prefix.
As Jürgen pointed out, the converters questions are targeted
by #558.
|
This is fixed in Zope 5.9.x. |
An textarea like
is converted by the new ZPublisher in Zope 4/Python 3 to list of byte strings instead of list of
str
.This is inconsistent with the default behavior of
<input type="text"> being returned as
strinside
request.form`.I think you could specify the encoding in older Zope versions like
name="mytext:lines:unicode">
orname=mytext:lines:utf8
however the specifying an encoding does not make a difference.The text was updated successfully, but these errors were encountered: