Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Terry Reedy
Jacob Rus wrote: Okay. Well I'd still like to hear a bit about what people really need before trying to make a new API. Try asking some specific question on python-list. "How to you use the stdlib mimetypes module?" ___ Python-Dev mailing list Pyt

Re: [Python-Dev] standard library mimetypes module pathol ogically broken?

2009-07-31 Thread Jacob Rus
Andrew McNabb wrote: > Jacob Rus wrote: >> * The operation is crazy: It defines a MimeTypes class which >> actually stores the type mappings, but this class is designed to >> be a singleton. The way that such a design is enforced is >> through the use of the module-global 'init' fu

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Jacob Rus
Brett Cannon wrote: > Jacob Rus wrote: >>  * It defines __all__: I didn’t even realize __all__ could be used >>    for single-file modules (w/o submodules), but it definitely >>    shouldn’t be here. > > __all__ is used to control what a module exports when used in an import *, > nothing more. Thus

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Jacob Rus
Brett Cannon wrote:  * It creates a _default_mime_types() function which declares a    bunch of global variables, and then immediately calls    _default_mime_types() below the definition. There is literally    no difference in result between this and just putting those    v

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Brett Cannon
On Fri, Jul 31, 2009 at 15:38, Jacob Rus wrote: > Brett Cannon wrote: > > Jacob Rus wrote: > >> * It defines __all__: I didn’t even realize __all__ could be used > >>for single-file modules (w/o submodules), but it definitely > >>shouldn’t be here. > > > > __all__ is used to control what

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread R. David Murray
On Fri, 31 Jul 2009 at 15:17, Brett Cannon wrote: * It creates a _default_mime_types() function which declares a bunch of global variables, and then immediately calls _default_mime_types() below the definition. There is literally no difference in result between this and just putting tho

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Andrew McNabb
On Fri, Jul 31, 2009 at 09:16:02PM +, Jacob Rus wrote: > > * The operation is crazy: It defines a MimeTypes class which > actually stores the type mappings, but this class is designed to > be a singleton. The way that such a design is enforced is > through the use of the m

Re: [Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Brett Cannon
On Fri, Jul 31, 2009 at 14:16, Jacob Rus wrote: > Hi all, > > In an attempt to figure out some twisted.web code, I was reading > through the Python Standard Library’s mimetypes module today, and > was shocked at the poor quality of the code. I wonder how the > mimetypes code made it into the stan

[Python-Dev] standard library mimetypes module pathologically broken?

2009-07-31 Thread Jacob Rus
Hi all, In an attempt to figure out some twisted.web code, I was reading through the Python Standard Library’s mimetypes module today, and was shocked at the poor quality of the code. I wonder how the mimetypes code made it into the standard library, and whether anyone has ever bothered to read it

[Python-Dev] Summary of Python tracker Issues

2009-07-31 Thread Python tracker
ACTIVITY SUMMARY (07/24/09 - 07/31/09) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2292 open (+33) / 16143 closed (+18) / 18435 total (+51) Open issues with patches: 899 Average