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 terry.reedy
Recipients BreamoreBoy, barry, ethan.furman, mark, serhiy.storchaka, terry.reedy
Date 2014-08-02.22:54:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407020064.07.0.677514386821.issue22123@psf.upfronthosting.co.za>
In-reply-to
Content
Making types.SimpleNamespace more easily available might be a good idea. Screwing around with our fundamental base class to do so is not.  Neither is rebinding the builtin name 'object'.  Find a different way to accomplish the goal.

SimpleNamespace *could* have been added to builtins, but was not.  Instead, it was added to types, which is the catchall for types not used enough to be in builtins.  Someone might check the issue or list discussion as to why.

At one time object had the bug of silently ignoring arguments. Years ago, Guido insisted that this be fixed and wrote patches himself. See #1683368. For one thing, raising the exception catches bugs with cooperative multiple inheritance and super calls. I believe having object() return a subclass of object that in not a superclass of other classes would be worse than the previous bug.

I think this idea should have been left on python-list or moved to python-ideas for further development.  I am sure that the proposal as stated should be rejected.
History
Date User Action Args
2014-08-02 22:54:24terry.reedysetrecipients: + terry.reedy, barry, mark, BreamoreBoy, ethan.furman, serhiy.storchaka
2014-08-02 22:54:24terry.reedysetmessageid: <1407020064.07.0.677514386821.issue22123@psf.upfronthosting.co.za>
2014-08-02 22:54:24terry.reedylinkissue22123 messages
2014-08-02 22:54:23terry.reedycreate