Re: [Tutor] 2.7.3 Popen argument issues

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 11:02 PM, eryksun wrote: > > out_file = "testing.avi" > out_ip = "127.0.0.1" > out_port = "11300" > dst_file = '"transcode{vb=400}:std{access=file,mux=avi,dst=%s}"' % out_file > dst_http = '"std{access=http,mux=mpjpeg,dst=%s:%s}"' % (out_ip, out_port) > sout = "'#duplicate{

Re: [Tutor] askopenfilename - columns missing in navigationwindow

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 9:56 PM, Joel Levine wrote: > > from tkFileDialog import askopenfilename > fn=askopenfilename() > > I use this program repeatedly. Up to a few hours ago, the navigation window > opened with a full array of columns, including name and date. > > Once I mistakenly typed cont

Re: [Tutor] 2.7.3 Popen argument issues

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 11:02 PM, eryksun wrote: > > import subprocess > > ip = "192.168.0.2" > port = "1234" > > out_file = "testing.avi" > out_ip = "127.0.0.1" > out_port = "11300" > dst_file = '"transcode{vb=400}:std{access=file,mux=avi,dst=%s}"' % out_file > dst_http = '"std{access=http,mux=mp

Re: [Tutor] 2.7.3 Popen argument issues

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 8:46 PM, Ray Jones wrote: > > Here is my Python call to vlc (error response to follow): > > vlcExec = sp.Popen(['vlc', 'http://' + ip + ':' + port, '-I dummy', > '--sout > \'#duplicate{dst="transcode{vb=400}:std{access=file,mux=avi,dst=outFile > + '.avi}",dst="std{access=ht

[Tutor] askopenfilename - columns missing in navigationwindow

2012-08-25 Thread Joel Levine
Mystery of the day: I'm using Python 2.6. My program uses from tkFileDialog import askopenfilename and fn=askopenfilename() I use this program repeatedly. Up to a few hours ago, the navigation window opened with a full array of columns, including name and date. Once I mistakenly typed con

[Tutor] 2.7.3 Popen argument issues

2012-08-25 Thread Ray Jones
Is there a method by which I can get an exact representation of command line arguments passed by Popen as seen by the called program? The argument error I receive shows me an argument that looks exactly like the argument that I use with Bash (it should - I copied and pasted it) - but the Bash versi

Re: [Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 1:39 PM, Alan Gauld wrote: > > two adjacent strings without a comma get combined into a single string. > Its a feature... mainly a remnant from the C foundations I suspect. As a feature it can come in handy with long strings in expressions. Just for reference about the "C

Re: [Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread Alan Gauld
On 25/08/12 16:53, aklei...@sonic.net wrote: in sequences of strings to prevent them from being "silently"<=>"concatenated" if you were to add an entry and forget the comma. error if the comma is omitted when adding an entry but I don't understand the (potential) concatenation problem. Cons

Re: [Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread akleider
Thanks for the clarification. Now it is clear. ak > On Sat, Aug 25, 2012 at 11:53 AM, wrote: >> >> Put each entry on its own line, indented by two spaces, and leave a >> trailing comma on the last entry. The latter is especially important >> in sequences of strings to prevent them from being >>

Re: [Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread eryksun
On Sat, Aug 25, 2012 at 11:53 AM, wrote: > > Put each entry on its own line, indented by two spaces, and leave a > trailing comma on the last entry. The latter is especially important > in sequences of strings to prevent them from being > "silently"<=>"concatenated" if you were to add an entry an

Re: [Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread Peter Otten
aklei...@sonic.net wrote: > Part of a previous post: > """ > Here's the style I'd use: > > combos = { > 0: 'id', > 2: 'country', > 3: 'type', > 5: 'lat', > 6: 'lon', > 12: 'name', > } > > Put each entry on its own line, indented by two spaces, and leave a > trailing comma on the last

[Tutor] reason(s) for trailing comma in dict declarations

2012-08-25 Thread akleider
Part of a previous post: """ Here's the style I'd use: combos = { 0: 'id', 2: 'country', 3: 'type', 5: 'lat', 6: 'lon', 12: 'name', } Put each entry on its own line, indented by two spaces, and leave a trailing comma on the last entry. The latter is especially important in sequences o

Re: [Tutor] Error message...

2012-08-25 Thread Victoria Homsy
Thank you everyone for your help with my question - I understand what I was doing wrong now. I know I'm posting wrongly so I'm going to go and figure out how to do it properly for the future. Have a great day. ___ Tutor maillist - Tutor@python.org To

Re: [Tutor] Error message...

2012-08-25 Thread Matthew Ngaha
>Hi Victoria. im a total beginner aswell but i noticed something. shouldnt this >line: else: return s(0) == s(-1) and isPalindrome (s[1:-1]) be else: return s[0] == s[-1] and isPalindrome (s[1:-1]) it looks like you have the string s as a function which you are trying to call. what you wante