John Gordon wrote:
> Looks like you need a comma after 'stdout=filename'.
Sigh, yesterday was a terrible day (yes, it lacks a comma)...
Anyway, when it is possible, is recommended to use the drivers for
communicate with databases, because subprocess (or os.*open*) is more
expensive compared to
Enrico 'Henryx' Bianchi wrote:
> cmd2 = subprocess.Popen(['gzip' '-c'],
> shell=False,
> stdout=filename)
Doh, my fault:
cmd2 = subprocess.Popen(['gzip' '-c'],
shell=False,
stdout=
MMZ wrote:
> config.read("~/my.cnf")
> username = config.get('client', 'mmz')
> password = config.get('client', 'pass1')
> hostname = config.get('client', 'localhost')
### A simple config file ###
[client]
user = mmz
password = pass1
host = localhost
### EOF ###
#!/usr/bin/env python
import Conf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven D'Aprano wrote:
> RHEL supports Python 3, it just doesn't provide Python 3.
True, but as you say later, the only method is to recompile. So, if I want
to use Python 3 in a production environment like RHEL, I need:
- A development environmen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobiah wrote:
> Use the newer version and don't look back.
Interesting reply, but if I have a platform wich doesn't support Python 3
(e.g. RHEL 5.x)? ]:)
Enrico
P.S. note that: I *don't* want to recompile Python in production environment
-BEGIN
