Package: geany
Version: 0.20-1.1
Severity: important
Hello The Hurd,
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 ?
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages geany depends on:
pn libatk1.0-0 <none> (no description available)
pn libc6 <none> (no description available)
pn libcairo2 <none> (no description available)
pn libfontconfig1 <none> (no description available)
pn libfreetype6 <none> (no description available)
pn libgcc1 <none> (no description available)
ii libgdk-pixbuf2.0-0 2.23.5-2 GDK Pixbuf library
pn libglib2.0-0 <none> (no description available)
pn libgtk2.0-0 <none> (no description available)
pn libpango1.0-0 <none> (no description available)
pn libstdc++6 <none> (no description available)
geany recommends no packages.
Versions of packages geany suggests:
pn doc-base <none> (no description available)
pn libvte9 <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
