This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients Jim.Jewett, eric.snow, gvanrossum, rhettinger, vstinner
Date 2012-03-25.23:15:13
SpamBayes Score 4.7084438e-08
Marked as misclassified No
Message-id <1332717314.39.0.0179359559553.issue14386@psf.upfronthosting.co.za>
In-reply-to
Content
I'm -1 on exposing this API.

Victor's sandboxing project doesn't warrant cluttering the public toolset.

As a consultant who gets to see many large codebases in different companies and I see zero need for this type to be exposed.  It is not hard to build proxies around any existing type.  Victor's use case is unique in that he needs the type to be implemented in C.  To that end, it would be okay to expose _dictproxy but not to make it a documented type.
History
Date User Action Args
2012-03-25 23:15:14rhettingersetrecipients: + rhettinger, gvanrossum, vstinner, eric.snow, Jim.Jewett
2012-03-25 23:15:14rhettingersetmessageid: <1332717314.39.0.0179359559553.issue14386@psf.upfronthosting.co.za>
2012-03-25 23:15:13rhettingerlinkissue14386 messages
2012-03-25 23:15:13rhettingercreate