On Fri, Jan 11, 2013 at 7:33 PM, Prasad, Ramit
wrote:
>
> Why not just use r'C:\Python27\\'? Might be too confusing for
> a beginner to remember, I suppose.
Off the top of my heard I can think of 3 raw-escape uses of backslash
in a raw string literal: placing an even number of backslashes at the
On 01/11/2013 07:33 PM, Prasad, Ramit wrote:
> [snip]
> Why not just use r'C:\Python27\\'? Might be too confusing for
> a beginner to remember, I suppose.
>
>
Because that'd have two trailing backslashes. (in Python 2.7 anyway)
--
DaveA
___
Tutor m
eryksun wrote:
[snip]
> 1. Using a forward slash in paths is OK for DOS/Windows system calls
> (e.g. opening a file or setting the cwd of a new process), dating back
> to the file system calls in MS-DOS 2.0 (1983). Otherwise a backslash
> is usually required (e.g. shell commands and paths in comman
On Wed, Jan 9, 2013 at 8:14 PM, T. Girowall wrote:
>
>
> c:\scripts\perl>perl plscript.pl -cmnd1 -cmnd2
>
> cmnd1 and cmnd2 are ran on files that reside within "perl" directory.
>
> My objective:
> 1. Run the perl script using python
> 2. Capture the results from the DOS window and save it to pyth
New to programing and need some help.
I have multiple perl script files that I would like to automate using python.
Currently each one is ran individually and the output is manually examined. The
perl script is ran form the command promp with arguments as follows:
c:\scripts\perl>perl plscr
