> > 1) I was wondering if anyone has opinions on the ability of
CGIHTTPServer (a
> > forking variant) to be able to handle this.
>
> Why not use apache?
Wanted something with less footprint.
--
http://mail.python.org/mailman/listinfo/python-list
Hi folks,
I'm looking build a CGI-capable SSL-enabled web-server around Python 2.4 on
Linux.
It is to handle ~25 hits possibly arriving "at once". Content is non-static
and built by the execution of py cgi-scripts talking to a few backend
processes.
1) I was wondering if anyone has opinions on th
> No. Hardly any HTTP 1.1 features are supported.
Hi all,
I'd like to know more about the limitations.
Somewhere, is there a list of the actual subset of HTTP 1.1 features
supported. There's not much related info at the python.org site. There
appears to be just a limited note on 1.1 in
http://ww
> I'd say Nevow! For apache setup, you might be interested in my wsgi [1]
> implementation.
Hi Sridhar,
Are you aware of Nevow's "integrability" with the webservers (CGIHTTPServer
in particular) that come packaged with Python itself ?
Thanks,
/venkat
--
http://mail.python.org/mailman/listinfo
Hi all,
I have a question re the use of Python to control a robot built with the
LEGO Mindstorm system.
This is to help my 11yr old with his increased interest in 'programming' and
'robotics'... If not feasible, he wants to use the graphical-tool that comes
with it...
Would you suggest:
1. Using
Hi all,
While building the latest 2.4.1 version for Linux/RH9, I wanted to enable
IPV6
support (sockets). So, I ran the configure command ./configure --enable-ipv6
Then I ran the 'make' and 'make altinstall' commands.
When I checked the .py sources (in Lib folder) thru grep for 'ipv6', I see
the
Hi folks,I have a webserver based on mini_httpd
v1.19(http://www.acme.com/software/mini_httpd/).I'd like to run some
python-based CGI scripts via this webserver on an RH9 system.In theory, with
the right env settings, Ishould be able to launch mini_httpd like so:
mini_httpd -c *.pyand be able to ru
We found the answer, just in case one was looking for it...
I turns out that setting the environment params (CGI_PATH & CGI_LD_LIB_PATH)
is not sufficient. One has to still add the path entry to the script
itself... like so: #! /python2.4
May also work with ensuring env variable PYTHONPATH is set
