Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Sun, 14 Apr 2013 04:22:49 -0700 (PDT)
In-Reply-To: <mailman.584.1365931737.3114.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=94.68.88.82; posting-account=hGu1uQoAAACZy7LiR653nG0NwqDrTyoS
References: <f6140a71-533e-4a6c-810d-6b8b1b046932@googlegroups.com> <mailman.584.1365931737.3114.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Unicode issue with Python v3.3
From: nagia.retsina@gmail.com
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: nagia.retsina@gmail.com, python-list@python.org
Precedence: list
Message-ID: <mailman.585.1365938578.3114.python-list@python.org>
Lines: 198
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:43570

=CE=A4=CE=B7 =CE=9A=CF=85=CF=81=CE=B9=CE=B1=CE=BA=CE=AE, 14 =CE=91=CF=80=CF=
=81=CE=B9=CE=BB=CE=AF=CE=BF=CF=85 2013 12:28:32 =CE=BC.=CE=BC. UTC+3, =CE=
=BF =CF=87=CF=81=CE=AE=CF=83=CF=84=CE=B7=CF=82 Cameron Simpson =CE=AD=CE=B3=
=CF=81=CE=B1=CF=88=CE=B5:
> On 13Apr2013 23:00, nagia.retsina@gmail.com <nagia.retsina@gmail.com> wro=
te:
>=20
> | root@nikos [/home/nikos/public_html/foo-py]# pwd
>=20
> | /home/nikos/public_html/foo-py
>=20
> | root@nikos [/home/nikos/public_html/foo-py]# cat foo.py=20
>=20
> | #!/bin/sh
>=20
> | exec 2>>/home/nikos/cgi.err.out
>=20
> | echo "$0 $*" >&2
>=20
> | id >&2
>=20
> | env | sort >&2
>=20
> | set -x
>=20
> | exec /full/path/to/foo-py ${1+"$@"}
>=20
> |=20
>=20
> | root@nikos [/home/nikos/public_html/foo-py]# python3 foo.py=20
>=20
> |   File "foo.py", line 2
>=20
> |     exec 2>>/home/nikos/cgi.err.out
>=20
> |          ^
>=20
> | SyntaxError: invalid syntax
>=20
>=20
>=20
> That is because foo.py isn't a python script anymore, it is a shell scrip=
t.
>=20
> Its purpose is to divert stderr to a file and to recite various
>=20
> things about the environment to that file in addition to any error
>=20
> messages.
>=20
>=20
>=20
> Just run it directly:
>=20
>=20
>=20
>   ./foo.py
>=20
>=20
>=20
> The #! line should cause it to be run by the shell.
>=20
>=20
>=20
> I also recommend you try to do all this as your normal user account.
>=20
> Root is for administration, such as stopping/starting apache and
>=20
> so on. Not test running scripts from the command line; consider:
>=20
> if the script has bugs, as root it can do an awful lot of damage.
>=20
>=20
>=20
> | root@nikos [/home/nikos/public_html/foo-py]#=20
>=20
> | As far as thr tail -f of the error_log:
>=20
> | root@nikos [/home/nikos/public_html]# touch /var/log/httpd/error_log
>=20
>=20
>=20
> That won't do you much good; apache has not opened it, and so it
>=20
> will not be writing to it. It was writing to a file of that name,
>=20
> but you removed that file. Apache probably still has its hooks in the old
>=20
> file (which now has no name).
>=20
>=20
>=20
> Restarting apache should open (or create if missing) this file for you.
>=20
>=20
>=20
> | root@nikos [/home/nikos/public_html]# tail -f /var/log/httpd/error_log
>=20
> | and its empty even when at the exact same time i run 'python3
>=20
> | metrites.py' from another interactive prompt when it supposed to
>=20
> | give live feed of the error messages.
>=20
>=20
>=20
> No, _apache_ writes to that file. So only when you visit the web
>=20
> page will stuff appear there.
>=20
>=20
>=20
> If you just run things from the command line, error messages will appear =
on your terminal. Or, after this line of the wrapper script:
>=20
>=20
>=20
>   exec 2>>/home/nikos/cgi.err.out
>=20
>=20
>=20
> the error messages will appear in cgi.err.out.
>=20
>=20
>=20
> | Cameron would it be too much to ask to provide you with root
>=20
> | access to my VPS server so you can have a look there too?
>=20
> | i can pay you if you like if you wait a few days to gather some money.
>=20
>=20
>=20
> I really do not recommend that:
>=20
>=20
>=20
>   - it is nuts to blithely allow a stranger root access to your system
>=20
>   - you won't learn anything about CGI scripts
>=20
>=20
>=20
> What you need for further debugging of your python issues is access
>=20
> to the error messages from the CGI script. That is the purpose of
>=20
> the wrapper script.
>=20
>=20
>=20
> Get the wrapper running on the command line and then test it via the brow=
ser.
>=20
>=20
>=20
> Cheers,
>=20
> --=20
>=20
> Cameron Simpson <cs@zip.com.au>
>=20
>=20
>=20
> Lord grant me the serenity to accept the things I can not change,
>=20
>      the courage to change the things that I can,
>=20
> and the wisdom to hide the bodies of those people I had to kill
>=20
>      because they pissed me off.
>=20
>         - Jeffrey Papen <JPapen@asucla.ucla.edu>

Well i trust you because you are the only one along with Lele that are help=
img me here:

i tried what you said:

root@nikos [/home/nikos/public_html/cgi-bin]# service httpd restart
root@nikos [/home/nikos/public_html/cgi-bin]# python3 metrites.py=20
root@nikos [/home/nikos/public_html]# cd foo-py/
root@nikos [/home/nikos/public_html/foo-py]# ls
./  ../  foo.py*
root@nikos [/home/nikos/public_html/foo-py]# ./foo.py=20
root@nikos [/home/nikos/public_html/foo-py]# cd ..
root@nikos [/home/nikos/public_html]# cat cgi.err.out=20
root@nikos [/home/nikos/public_html/cgi-bin]# cat /var/log/httpd/error_log=
=20
root@nikos [/home/nikos/public_html/cgi-bin]#=20

and i have run the script form browser but i still see nothing.

I insist that you will make the most of this if you access the VPS yourself=
.
it runs CentOS 6.4

Please accept, i trust you.