Re: python 2.7.12 on Linux behaving differently than on Windows

2016-12-04 Thread Gregory Ewing
Steve D'Aprano wrote: On Mon, 5 Dec 2016 07:26 am, DFS wrote: no such column: R doesn't this mean that your column is called: single quote R single quote I think he intends it to be an SQL string literal (which uses single quotes), but since the quotes disappeared, SQL is trying to

Re: python 2.7.12 on Linux behaving differently than on Windows

2016-12-04 Thread Chris Angelico
On Mon, Dec 5, 2016 at 9:19 AM, BartC wrote: > Command parameters /do/ behave differently between Windows and Linux, for > example try writing *.* as that third parameter. > > In Windows, it will print *.*. > > In Linux, if you have 273 files in the current directory, if will

Re: python 2.7.12 on Linux behaving differently than on Windows

2016-12-04 Thread Steve D'Aprano
On Mon, 5 Dec 2016 07:26 am, DFS wrote: > $python program.py column1=2174 and column2='R' Here is a simple script demonstrating the issue: # --- program.py --- import sys print "argv:", sys.argv print ' '.join(sys.argv[1:]) I haven't tested it on Windows, but on Linux it behaves as you

Re: python 2.7.12 on Linux behaving differently than on Windows

2016-12-04 Thread BartC
On 04/12/2016 20:26, DFS wrote: $python program.py column1=2174 and column2='R' Windows (correct) $print sys.argv[3] column2='R' Linux (incorrect) $print sys.argv[3] column2=R It drops the apostrophes, and the subsequent db call throws an error: sqlite3.OperationalError: no such column: R

<    1   2   3