[jira] [Commented] (CASSANDRA-15802) Commented-out lines that end in a semicolon cause an error.

2020-05-20 Thread null (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17112299#comment-17112299
 ] 

null  commented on CASSANDRA-15802:
---

Thanks [~RensGroothuijsen] and [~jwest] for your comments on this. Any idea how 
it can be patched? [~djoshi] any ideas?

This is the only thing holding me back from moving away from Python 2.7

thanks! :)

> Commented-out lines that end in a semicolon cause an error.
> ---
>
> Key: CASSANDRA-15802
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15802
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Interpreter, CQL/Syntax
>Reporter: null 
>Priority: Normal
> Attachments: cqlsh.png
>
>
> Commented-out lines that end in a semicolon cause an error.
> For example:
> /*
> describe keyspaces;
> */
>  
> This produces an error:
> SyntaxException: line 2:22 no viable alternative at input ' (...*
> describe keyspaces;...)
>  
> It works as expected if you use syntax:
> -- describe keyspaces;
>  
> Environment:
> python:3.7.7-slim-stretch (docker image)
>  
> I found that this was first seen here, and was patched, but the bug appears 
> to have resurfaced:
> https://issues.apache.org/jira/browse/CASSANDRA-2488



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15802) Commented-out lines that end in a semicolon cause an error.

2020-05-12 Thread null (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105139#comment-17105139
 ] 

null  commented on CASSANDRA-15802:
---

Agreed, you're right Jordan. I did have a look through the cqlsh.py and see if 
I could spot where to patch it.

I found the "self.in_comment" flag but this doesn't ever appear to be set to 
anything other than false, so I'm not sure if this is deprecated? Or maybe the 
fact its never set might be the problem?

> Commented-out lines that end in a semicolon cause an error.
> ---
>
> Key: CASSANDRA-15802
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15802
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Interpreter, CQL/Syntax
>Reporter: null 
>Priority: Normal
> Attachments: cqlsh.png
>
>
> Commented-out lines that end in a semicolon cause an error.
> For example:
> /*
> describe keyspaces;
> */
>  
> This produces an error:
> SyntaxException: line 2:22 no viable alternative at input ' (...*
> describe keyspaces;...)
>  
> It works as expected if you use syntax:
> -- describe keyspaces;
>  
> Environment:
> python:3.7.7-slim-stretch (docker image)
>  
> I found that this was first seen here, and was patched, but the bug appears 
> to have resurfaced:
> https://issues.apache.org/jira/browse/CASSANDRA-2488



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Created] (CASSANDRA-15802) Commented-out lines that end in a semicolon cause an error.

2020-05-11 Thread null (Jira)
null  created CASSANDRA-15802:
-

 Summary: Commented-out lines that end in a semicolon cause an 
error.
 Key: CASSANDRA-15802
 URL: https://issues.apache.org/jira/browse/CASSANDRA-15802
 Project: Cassandra
  Issue Type: Bug
  Components: CQL/Interpreter, CQL/Syntax
Reporter: null 
 Attachments: cqlsh.png

Commented-out lines that end in a semicolon cause an error.

For example:

/*

describe keyspaces;

*/

 

This produces an error:

SyntaxException: line 2:22 no viable alternative at input ' (...*
describe keyspaces;...)

 

It works as expected if you use syntax:

-- describe keyspaces;

 

Environment:

python:3.7.7-slim-stretch (docker image)

 

I found that this was first seen here, and was patched, but the bug appears to 
have resurfaced:

https://issues.apache.org/jira/browse/CASSANDRA-2488



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-10190) Python 3 support for cqlsh

2019-09-27 Thread null (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939184#comment-16939184
 ] 

null commented on CASSANDRA-10190:
--

Thanks for working on this, I can't believe cqlsh is limited to Python 2.7, 
seems crazy when 1st January 2020 isn't too far away.

How far away are you from a working cqlsh on Python 3.x?

thanks again for your great work on this :)

> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
>  Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh. 
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a 
> .python-version containing "2.7". But it would be nice if cqlsh supported 
> modern Python versions out of the box.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org