<div><span class="q"><span class="gmail_quote">On 5/30/06, <b class="gmail_sendername">Steven Bethard</b> <<a href="mailto:steven.bethard@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
steven.bethard@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 5/30/06, Brett Cannon <<a href="mailto:brett@python.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">brett@python.org</a>> wrote:<br>> So, first step in my mind is settling if we want to add one more depth to
<br>> the stdlib, and if so, how we want to group (not specific groupings, just
<br>> general guidelines).<br><br>I think that having a package level that exactly matches the divisions<br>in the Library Reference (<a href="http://docs.python.org/lib/lib.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://docs.python.org/lib/lib.html</a>
) would<br>be great. </blockquote></span></div><div><div><br><br>Makes sense to me.<br> </div></div><div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Currently, that would mean packages for:
<br><br>3. Python Runtime Services<br>4. String Services<br>5. Miscellaneous Services</blockquote></span></div><div><div><br>I
don't think we necessarily want a misc package. Should stuff that
falls into here just be at the root level? Besides, some stuff, such as
heapq, bisect, collections, and the User* modules could got into a data
structure package. I also think that a testing package would make
sense. Could also have a math package.
<br></div></div><div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">6. Generic Operating System Services<br>7. Optional Operating System Services
</blockquote>
</span></div><div><div><br>This includes socket, which I would think
would belong more in a networking-centric package (not including
web-specific stuff). Plus I believe a threading/concurrency package
has been proposed before (which included hiding 'thread' so that people
wouldn't use such low-level stuff).
<br></div></div><div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">8. Unix Specific Services<br>9. The Python Debugger
<br>10. The Python Profiler
</blockquote></span></div><div><div><br>Can't the pdb and profiling going into a developer package? </div></div><div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
11. Internet Protocols and Support</blockquote></span></div><div><div><br>Should xmlrpclib be in here, or in something more in line with RPC and "concurrency"?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
12. Internet Data Handling</blockquote><div><br>Should we merge this with a more generic Internet/Web package? Have a separate email package that includes 'email', smtp, etc?<br></div></div><div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
13. Structured Markup Processing Tools<br>14. Multimedia Services<br>15. Cryptographic Services<br>16. Graphical User Interfaces with Tk<br>17. Restricted Execution</blockquote></span></div><div><div><br>=) This section's not really valid anymore (although I will be fixing that at some point).
<br></div></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">18. Python Language Services<br>19. Python compiler package
<br>20. SGI IRIX Specific Services
<br>21. SunOS Specific Services<br>22. MS Windows Specific Services<br></blockquote></span>