[
https://issues.apache.org/jira/browse/CASSANDRA-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
paul cannon updated CASSANDRA-3846:
-----------------------------------
Description:
Kris Hahn discovered a python2.6-ism in recent cqlsh changes:
{code}
bval = escapedval.encode(output_encoding, errors='backslashreplace')
{code}
before python2.7, str.encode() didn't accept a keyword argument for the second
parameter. the semantics are the same without naming the parameter, though, so
removing the "errors=" bit should suffice to make it run right.
does not affect any released version, but does affect HEAD of cassandra-1.0,
cassandra-1.1, and trunk.
was:
Kris Hahn discovered a python2.6-ism in recent cqlsh changes:
{code}
bval = escapedval.encode(output_encoding, errors='backslashreplace')
{code}
python2.5's str.encode() doesn't accept a keyword argument for the second
parameter. the semantics are the same without naming the parameter, though, so
removing the "errors=" bit should suffice to make it run right.
does not affect any released version, but does affect HEAD of cassandra-1.0,
cassandra-1.1, and trunk.
Summary: cqlsh can't show data under python2.5, python2.6 (was: cqlsh
can't show data under python2.5)
edit: this is also a problem on python2.6, not just python2.5. resolution is
still the same.
> cqlsh can't show data under python2.5, python2.6
> ------------------------------------------------
>
> Key: CASSANDRA-3846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3846
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.0.8
>
> Attachments: 3846.patch.txt
>
>
> Kris Hahn discovered a python2.6-ism in recent cqlsh changes:
> {code}
> bval = escapedval.encode(output_encoding, errors='backslashreplace')
> {code}
> before python2.7, str.encode() didn't accept a keyword argument for the
> second parameter. the semantics are the same without naming the parameter,
> though, so removing the "errors=" bit should suffice to make it run right.
> does not affect any released version, but does affect HEAD of cassandra-1.0,
> cassandra-1.1, and trunk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
