Re: PEP 594 cgi & cgitb removal

2019-06-01 Thread Peter J. Holzer
On 2019-05-25 23:45:06 +0200, Roel Schroeven wrote: > Jon Ribbens via Python-list schreef op 25/05/2019 om 21:00: > > On 2019-05-25, Michael Torrie wrote: > > > On 05/24/2019 04:27 AM, Jon Ribbens via Python-list wrote: > > > > Sorry, in what sense do you mean "Serverless is CGI"? > > > > > > >

Re: PEP 594 cgi & cgitb removal

2019-05-29 Thread Robin Becker
... More specifically, with CGI the webserver starts a new process for every single request. That's bad enough for a light C program, but it's certainly not a good idea to start a whole new Python process for every request. At least not for any production website or web service that

Re: PEP 594 cgi & cgitb removal

2019-05-28 Thread Rhodri James
On 24/05/2019 21:23, Terry Reedy wrote: I am responding to Paul indirectly because his post did not show up on the gmane mirror. Paul Rubin : It also makes me ask why the Python team keeps adding new stuff if it can't even keep the old stuff running. Because the new stuff is expected to

Re: PEP 594 cgi & cgitb removal

2019-05-25 Thread Roel Schroeven
Jon Ribbens via Python-list schreef op 25/05/2019 om 21:00: On 2019-05-25, Michael Torrie wrote: On 05/24/2019 04:27 AM, Jon Ribbens via Python-list wrote: Sorry, in what sense do you mean "Serverless is CGI"? As far as I can tell, it's just a script to automatically upload bits of code into

Re: PEP 594 cgi & cgitb removal

2019-05-25 Thread Marko Rauhamaa
Jon Ribbens : > On 2019-05-25, Michael Torrie wrote: >> Not really. Serverless just means stateless web-based remote >> procedure calls. This is by definition what CGI is. > > No, it isn't. CGI is a specific API and method of calling a program in > order to serve a web request. It isn't a

Re: PEP 594 cgi & cgitb removal

2019-05-25 Thread Jon Ribbens via Python-list
On 2019-05-25, Michael Torrie wrote: > On 05/24/2019 04:27 AM, Jon Ribbens via Python-list wrote: >> Sorry, in what sense do you mean "Serverless is CGI"? >> >> As far as I can tell, it's just a script to automatically upload >> bits of code into various cloud providers, none of which use CGI. >

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Michael Torrie
On 05/24/2019 04:27 AM, Jon Ribbens via Python-list wrote: > On 2019-05-23, Gunnar Þór Magnússon wrote: >>> nginx is the current hotness. CGI has not been hotness since the >>> mid 90s. >> >> Serverless is the new hotness, and serverless is CGI. Technology is >> cyclical. > > Sorry, in what

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Michael Torrie
On 05/24/2019 01:24 PM, Marko Rauhamaa wrote: > There's a programming language arms race. Python wants to beat Java, C# > and go in the everything-for-everybody game. Python developers seem to > take the popularity of the language as proof of success. Pride goes > before the fall. I don't see

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Terry Reedy
I am responding to Paul indirectly because his post did not show up on the gmane mirror. Paul Rubin : It also makes me ask why the Python team keeps adding new stuff if it can't even keep the old stuff running. Because the new stuff is expected to be more useful to more people than some

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Marko Rauhamaa
Paul Rubin : > Stéphane Wirtel writes: >> Not a massive effort, but we are limited with the resources. > > I keep hearing that but it makes it sound like Python itself is in > decline. That is despite the reports that it is now the most popular > language in the world. It also makes me ask why

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread D'Arcy Cain
On 2019-05-22 03:51, Robin Becker wrote: > In PEP 594 t has been proposed that cgi & cgitb should be removed. I > suspect I am not the only person in the world that likes using cgi and > cgitb. I use both heavily. Just another data point. I wasn't going to respond with a "Me too" except that I

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Stéphane Wirtel
On 05/23, Rhodri James wrote: On 22/05/2019 19:29, Terry Reedy wrote: One of the factors being considered in removal decisions is the absence of anyone willing to list themselves in the expert's list https://devguide.python.org/experts/ as a maintainer for a module. At the moment, 3 other

Re: PEP 594 cgi & cgitb removal

2019-05-24 Thread Jon Ribbens via Python-list
On 2019-05-23, Gunnar Þór Magnússon wrote: >> nginx is the current hotness. CGI has not been hotness since the >> mid 90s. > > Serverless is the new hotness, and serverless is CGI. Technology is > cyclical. Sorry, in what sense do you mean "Serverless is CGI"? As far as I can tell, it's just a

Re: PEP 594 cgi & cgitb removal

2019-05-23 Thread Gunnar Þór Magnússon
> nginx is the current hotness. CGI has not been hotness since the mid 90s. Serverless is the new hotness, and serverless is CGI. Technology is cyclical. -- https://mail.python.org/mailman/listinfo/python-list

Re: PEP 594 cgi & cgitb removal

2019-05-23 Thread Rhodri James
On 22/05/2019 19:29, Terry Reedy wrote: One of the factors being considered in removal decisions is the absence of anyone willing to list themselves in the expert's list https://devguide.python.org/experts/ as a maintainer for a module. At the moment, 3 other people have objected to the

Re: PEP 594 cgi & cgitb removal

2019-05-23 Thread Jon Ribbens via Python-list
On 2019-05-23, Paul Rubin wrote: > dieter writes: >> Should "cgi" disappear from the standard library > > It's also a concern that cgi may be disappearing from web servers. Last > I heard, nginx didn't support it. That's part of why I still use > apache, or (local only) even CGIHTTPServer.py.

Re: PEP 594 cgi & cgitb removal

2019-05-22 Thread dieter
Robin Becker writes: > In PEP 594 t has been proposed that cgi & cgitb should be removed. I > suspect I am not the only person in the world that likes using cgi and > cgitb. Currently, "Zope" is using "cgi"; it uses "zExceptions" (--> PyPI) for tracebacks. Should "cgi" disappear from the

Re: PEP 594 cgi & cgitb removal

2019-05-22 Thread Terry Reedy
On 5/22/2019 3:51 AM, Robin Becker wrote: In PEP 594 t has been proposed that cgi & cgitb should be removed. I suspect I am not the only person in the world that likes using cgi and cgitb. I suspect that there will be at least one person objecting to each removal. But the underlying issue,

Re: PEP 594 cgi & cgitb removal

2019-05-22 Thread Tim Chase
On 2019-05-22 08:51, Robin Becker wrote: > In PEP 594 t has been proposed that cgi & cgitb should be removed. > I suspect I am not the only person in the world that likes using > cgi and cgitb. /me waves from the the back row as another cgi/cgitb user... -tkc --

Re: PEP 594 cgi & cgitb removal

2019-05-22 Thread inhahe
Re cgitb, not sure if this is what you want, but I just came across this this week: https://github.com/cknd/stackprinter On Wed, May 22, 2019 at 3:52 AM Robin Becker wrote: > In PEP 594 t has been proposed that cgi & cgitb should be removed. I > suspect I am not the only person in the world

Re: PEP 594 cgi & cgitb removal

2019-05-22 Thread Rhodri James
On 22/05/2019 08:51, Robin Becker wrote: In PEP 594 t has been proposed that cgi & cgitb should be removed. I suspect I am not the only person in the world that likes using cgi and cgitb. Can I second this? I just started writing a small CGI application in Python, and if cgi and cgitb were

PEP 594 cgi & cgitb removal

2019-05-22 Thread Robin Becker
In PEP 594 t has been proposed that cgi & cgitb should be removed. I suspect I am not the only person in the world that likes using cgi and cgitb. One of the nice features in cgitb is the ability to get a nice traceback with variable values etc etc etc. I have used the underlying mechanism to