<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 22 Mar 2017, at 12:51, George Fischhof <<a href="mailto:george@fischhof.hu" class="">george@fischhof.hu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi Guys,<br class=""><br class=""></div>I would like to ask You:<br class="">What is the process to propose a module to be part of the standard library?<br class=""><br class=""></div>I would like to propose the following modules:<br class=""></div>requests<br class=""><a href="https://pypi.python.org/pypi/requests" class="">https://pypi.python.org/pypi/requests</a><br class=""></div></div></div></div></div></div></div></div></blockquote><br class=""></div><div>Thanks for the consideration, and we’re glad that you find Requests helpful. However, the Requests project is not interested in being part of the standard library for as long as it’s under active development. This LWN article provides a good summary of the discussion that was had at the 2015 Python Language Summit, which covers the arguments for and against: <a href="https://lwn.net/Articles/640838/" class="">https://lwn.net/Articles/640838/</a>.</div><div><br class=""></div><div>We believe that the most important place to spend time is not adding more modules to the standard library, but making it easier to get hold of the best-in-class third-party modules.</div><div><br class=""></div><div>Cory</div><br class=""></body></html>