> When called with -c command, it executes the Python statement(s) given as command. Here command may contain multiple statements separated by newlines. Leading whitespace is significant in Python statements!
So you should replace the semicolon with newline.
BTW, the loop can be simplified using `enumerate` like this:
> Hello list. I'm a newbie when it comes to Python.
> I'm trying to turn this:
> def print_sys_path():
> i = 0
> for p in sys.path:
> print ('sys.path[%2d]: %s' % (i, p))
> i += 1
> into a one-line python command (in a .bat file):
> python -c "import sys,os; i=0; for p in sys.path:
> print('sys.path[%%2d]: %%s' %% (i, p)); i+=1"
> But:
> File "<string>", line 1
> import sys,os; i=0; for p in sys.path: print('sys.path[%2d]: %s' %
> (i, p)); i+=1
> ^
> SyntaxError: invalid syntax
> The caret is on the 'for'. What's the problem?
> --gv
it has nothing to do with being on a command line. You're using
semicolon to combine several statements, and there are restrictions on
what can be combined that way. One restriction is the looping
constructs, for, if, while.
Try experimenting with a standard program, to see what can be combined
and what cannot.
You can do it easily enough with a list comprehension. Let us know if
you can't work that out.
By the way, much cleaner than defining your own counting variable is to
use enumerate().
Any reason why you don't just make a one-file python script, and run
that instead of your one line batch file? Or is this line one of many
in the batch file?
Gisle Vanem <gva...@broadpark.no> wrote:
> Hello list. I'm a newbie when it comes to Python.
> I'm trying to turn this:
> def print_sys_path():
> i = 0
> for p in sys.path:
> print ('sys.path[%2d]: %s' % (i, p))
> i += 1
> into a one-line python command (in a .bat file):
Is "one liner" an actual requirement or is the requirement to run it
from the command line?
python -c "
import sys
i = 0
for p in sys.path:
print('sys.path[%2d]: %s' % (i, p))
i+=1
"
I don't know if this works on Windows or not.
-- D'Arcy J.M. Cain <da...@druid.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
IM: da...@Vex.Net
> On Thu, 11 Oct 2012 13:24:22 +0200
> Gisle Vanem <gva...@broadpark.no> wrote:
>> Hello list. I'm a newbie when it comes to Python.
>> I'm trying to turn this:
>> def print_sys_path():
>> i = 0
>> for p in sys.path:
>> print ('sys.path[%2d]: %s' % (i, p))
>> i += 1
>> into a one-line python command (in a .bat file):
> Is "one liner" an actual requirement or is the requirement to run it
> from the command line?
> python -c "
> import sys
> i = 0
> for p in sys.path:
> print('sys.path[%2d]: %s' % (i, p))
> i+=1
> "
> I don't know if this works on Windows or not.
It doesn't, I just tested it. Windows batch is appallingly crude
compared to a modern Unix shell; you may be able to find a way to get
around this, but the easiest solution for most batch files is going to
be an actual Python script file. You may be able to overlay your batch
and Python scripts with a trick like this:
rem = '''
@echo off
echo This is batch
\python32\python %0
echo All done
exit /b
rem '''
import sys
print("This is Python")
for i,p in enumerate(sys.path):
print('sys.path[%2d]: %s' % (i, p))
print("Python done")
You'll have a variable in Python called 'rem' which contains all your
batch code :) It exploits the fact that 'rem' makes a one-line
comment, but the triple quotes go across multiple lines. (The "exit
/b" should exit the batch script without closing cmd.exe - this is yet
another weird WEIRD wart in Windows batch. I'm pretty sure neither DOS
nor OS/2 batch required that parameter.)
<maniandra...@gmail.com> wrote:
> What about the "Power" in PowerShell?
What about it? Are you suggesting that the OP use it? Are you saying
that Windows batch already includes it? You quoted my entire post
(double-spaced), but that context adds nothing to your statement; it
still stands alone as a complete non sequitur.
"Dave Angel" <d...@davea.name> wrote:
> it has nothing to do with being on a command line. You're using
> semicolon to combine several statements, and there are restrictions on
> what can be combined that way. One restriction is the looping
> constructs, for, if, while.
Ok, I suspected something like that.
> You can do it easily enough with a list comprehension. Let us know if
> you can't work that out.
Later. I'm only scratching the surface of Python.
> Any reason why you don't just make a one-file python script, and run
> that instead of your one line batch file?
I though of calling that python line from a C-program using
popen() and parsing the output. Since popen() on Win32 AFAIK doesn't accept multiple lines, I guess I must write a .py-file to %TEMP first.
(my ISP no longer updates this group. Last message is from 8. April.
Does the postings to the python mailing-list automatically get reposted to comp.lang.python?)
On Fri, Oct 12, 2012 at 3:49 AM, Gisle Vanem <gva...@broadpark.no> wrote:
> <wxjmfa...@gmail.com> wrote in comp.lang.python
> (my ISP no longer updates this group. Last message is from 8. April.
> Does the postings to the python mailing-list automatically get reposted to
> comp.lang.python?)
Presumably it's so that I can zip up my entire Python library and toss
it into a convenient file. I don't think it costs much to stat a file
and find it's not there before moving on, so it's not a problem to
leave it there.
Chris Angelico wrote:
> On Fri, Oct 12, 2012 at 3:49 AM, Gisle Vanem <gva...@broadpark.no> wrote:
> > <wxjmfa...@gmail.com> wrote in comp.lang.python
> > (my ISP no longer updates this group. Last message is from 8. April.
> > Does the postings to the python mailing-list automatically get reposted to
> > comp.lang.python?)
> Presumably it's so that I can zip up my entire Python library and toss
> it into a convenient file. I don't think it costs much to stat a file
> and find it's not there before moving on, so it's not a problem to
> leave it there.
> ChrisA
Interesting, my results are slightly different. Here is what I get from (one of) my Python installs.
2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)]
C:\ramit\Python27\python27.zip
C:\ramit\Python27\DLLs
C:\ramit\Python27\lib
C:\ramit\Python27\lib\plat-win
C:\ramit\Python27\lib\lib-tk
C:\ramit\Python27
C:\ramit\Python27\lib\site-packages
Ramit
This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.
>> it has nothing to do with being on a command line. You're using
>> semicolon to combine several statements, and there are restrictions on
>> what can be combined that way. One restriction is the looping
>> constructs, for, if, while.
> Ok, I suspected something like that.
>> You can do it easily enough with a list comprehension. Let us know if
>> you can't work that out.
> Later. I'm only scratching the surface of Python.
>> Any reason why you don't just make a one-file python script, and run
>> that instead of your one line batch file?
> I though of calling that python line from a C-program using
> popen() and parsing the output. Since popen() on Win32 AFAIK doesn't
> accept multiple lines, I guess I must write a .py-file to %TEMP first.
> Thank to all.
> --gv
Why would you write some C-program just to save having two separate
files, one batch and one for the script? For that matter, several
answers have given you approaches that didn't involve list
comprehensions, including merging the two in a single file, using an
initial variable of rem="""
What are your real constraints? Are you just playing code-golf?
"Dave Angel" <d...@davea.name> wrote:
> Why would you write some C-program just to save having two separate
> files, one batch and one for the script? For that matter, several
> answers have given you approaches that didn't involve list
> comprehensions, including merging the two in a single file, using an
> initial variable of rem="""
Like I wrote; use popen() or system() from a C-program (an env-var
checker) that's not really related to Python programming. But rather to check various stuff needed for C-programming . Like walking the list of %INCLUDE / %C_INCLUDE_PATH dirs to figure out what headers are where. So I'd just as well add an option to check for Python paths too (if Python is installed that is).
> What are your real constraints? Are you just playing code-golf?
