Installation on Linux - how?

[Chris Green]

I'm trying to follow the installation instructions on the firedrop2
web site but they're *very* Windows oriented.

I have python 2.4.3 and wxpython 2.6.3.3 installed already (and
working, I have quite a few python things already). I've installed
wax, that seems straightforward. However it gets a bit less simple
when I get to firedrop2 itself.

I've put the firedrop2 directory into my python site packages
directory and I have unscrambled the permissions so files are
executable. Then I hit the problems:-

One doesn't really 'double click' on things in Linux, well it's
possible but it's not really 'the way'. :-)

So I tried running firedrop.pyw, not a hope, it's a Windows format
file with CR/LF line terminators so all the 'blank' lines (which
aren't blank in Linux) give errors. I've edited them to be just LF
and then it just errors on the try: at line 21.

Where do I go now, I'm stuck.

[Michael Foord]

What is the actual error message ?

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

> >
>

[Eur Ing Chris Green]

home$ firedrop.pyw
/home/chris/bin/firedrop.pyw: line 21: try:: command not found

home$

Note that after the "command not found" error above I have to hit
CTRL/C to get back to the command prompt.

All that's happening (as far as I can see) is that firedrop.pyw is
being run as a shell script, it's what one would expect as there's no
bang path on the first line.

What is *supposed* to be running firedrop.pyw?

--
Chris Green

[Michael Foord]

Python :-)

In windows you have file associations rather than pound bang lines.

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

[Eur Ing Chris Green]

Oh dear, a bit obvious that really! It's just that I was thinking that
.pyw indicated something different from plain python (i.e. some sort
of wxPython or wax wrapper).

> In windows you have file associations rather than pound bang lines.
>

In Linux you have bang paths rather than file associations! :-)

To work in Linux firedrop.pyw needs the bang path or you need to say:-

python firedrop.pyw

It's up and running now, thank you.

--
Chris Green

[Michael Foord]

Eur Ing Chris Green wrote:
> On Wed, Mar 07, 2007 at 11:17:37AM +0000, Michael Foord wrote:
>
>> Eur Ing Chris Green wrote:
>>
>>> On Tue, Mar 06, 2007 at 11:33:19PM +0000, Michael Foord wrote:
>>>
>>>> What is the actual error message ?
>>>>
>>>> Fuzzyman
>>>> http://www.voidspace.org.uk/python/articles.shtml
>>>>
>>>>
>>>>
>>> home$ firedrop.pyw
>>> /home/chris/bin/firedrop.pyw: line 21: try:: command not found
>>>
>>> home$
>>>
>>> Note that after the "command not found" error above I have to hit
>>> CTRL/C to get back to the command prompt.
>>>
>>> All that's happening (as far as I can see) is that firedrop.pyw is
>>> being run as a shell script, it's what one would expect as there's no
>>> bang path on the first line.
>>>
>>> What is *supposed* to be running firedrop.pyw?
>>>
>>>
>> Python :-)
>>
>>
> Oh dear, a bit obvious that really! It's just that I was thinking that
> .pyw indicated something different from plain python (i.e. some sort
> of wxPython or wax wrapper).
>
>
>

It's the windows way of saying 'run me with pythonw.exe instead of
python.exe'.

Sorry about that.

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml