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 berker.peksag
Recipients berker.peksag, ghaering, palaviv, r.david.murray
Date 2017-05-05.18:46:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494010014.0.0.199090624669.issue30262@psf.upfronthosting.co.za>
In-reply-to
Content
> Someone somewhere may be using them for something, they've been around for a long time.

Well, you can use the same argument for every issue on the tracker. People can even rely on real bugs that are still open for 10 years, but that doesn't mean they shouldn't be fixed.

In this case, your argument looks a bit hypothetical to me. I can't think of valid usages of these objects (I understand people can abuse Python's dynamic nature, but still... :)) You've obviously spent much more time working on sqlite3 than me so I wonder how can they can be useful to third party users :) (e.g. can someone use them for some reason to test their enhanced version of pydoc's extension module support?)
History
Date User Action Args
2017-05-05 18:46:54berker.peksagsetrecipients: + berker.peksag, ghaering, r.david.murray, palaviv
2017-05-05 18:46:54berker.peksagsetmessageid: <1494010014.0.0.199090624669.issue30262@psf.upfronthosting.co.za>
2017-05-05 18:46:53berker.peksaglinkissue30262 messages
2017-05-05 18:46:53berker.peksagcreate