<div dir="ltr"><div>I still like http.server for quick temporary hacks where I want to be able to point a browser at some code I wrote 5 minutes ago and that I plan to discard in an hour. Usually it's running at localhost:8000. Remembering how to use Django, flask or Tornado seems overkill for that purpose.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 21, 2019 at 9:39 AM Glenn Linderman <<a href="mailto:v%2Bpython@g.nevcal.com">v+python@g.nevcal.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_-1579688106735782448moz-cite-prefix">On 5/20/2019 2:20 PM, Christian Heimes
wrote:<br>
</div>
<blockquote type="cite">
<pre class="gmail-m_-1579688106735782448moz-quote-pre">On 20/05/2019 23.12, Andrew Svetlov wrote:
</pre>
<blockquote type="cite">
<pre class="gmail-m_-1579688106735782448moz-quote-pre">socketserver.py is also questionable
</pre>
</blockquote>
<pre class="gmail-m_-1579688106735782448moz-quote-pre">I briefly though about the module, but didn't consider it for removal. The http.server, xmlrpc.server, and logging configuration server are implemented on top of the socketserver. I don't want to remove the socketserver module without a suitable replacement for http.server in the standard library.</pre>
</blockquote>
<br>
But http.server could be on the remove list too... it gets mighty
little support, has very little functionality, and implements a CGI
interface (although that also has very little functionality), and
you have the CGI tools on the remove list, rendering the CGI
interface implemented by http.server less easily usable.<br>
<br>
Further, it doesn't directly support https:, and browsers are
removing/reducing support for http:.<br>
<br>
I can't speak to xmlrpc or logging configuration.<br>
<br>
<br>
<br>
<br>
</div>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/guido%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/mailman/options/python-dev/guido%40python.org</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div><div><i style="font-family:Arial,Helvetica,sans-serif;font-size:small;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);color:rgb(136,136,136)"><span>Pronouns</span>: he/him/his </i><a href="http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/" style="color:rgb(17,85,204);font-family:Arial,Helvetica,sans-serif;font-size:small;font-style:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)" target="_blank"><i>(why is my <span>pronoun</span> here?)</i></a></div></div></div>