On Thu, 04 Aug 2011 16:56:23 +0200, Valentin wrote: Hi,
>The day before yesterday I noticed the trouble following:
>
>When I use the 'geany' programming editor, whenever I want to execute a
>Python script, it always use the default version of the interpretor:
> ver. 2.6.7 (r267.88850, Jul 10 2011, 08:11:54) [GCC 4.6.1]
> (it's the default interpreter version under Debian testing)
>even when the script begins with:
> #! /usr/bin/env python3
>
>I would have preferred the following:
>
> ver. 3.2.1 (default, Jul 10 2011, 20:12:44) [GCC 4.6.1]
> ( Which is installed on my system, of course. )
>
>Important note Part I : If I execute the same script from the shell,
>it is run byt under the right version of the Python interpreter
>(assuming octal 500 permissions at least).
>
>Important note Part II : If I type "env python3", or just "python3",
>this launches the expected 3.2... version of the Python interpreter.
>
>Any fixup in mind ?
No, since it's not a bug.
Geany won't evaluate the shebang when executing Python, Shell or
whatever scripts and this is why your #!/usr/bin/env line has no effect.
Instead, Geany uses the configured command in Build->Set Build Commands
to execute the script.
There you can easily change the default ("python") to "python3" or
whatever you want.
See also Geany's documentation about the build system.
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
pgpveImruDNyI.pgp
Description: PGP signature
