[issue3181] ConfigParsers are classic classes

2008-07-20 Thread Georg Brandl
Georg Brandl <[EMAIL PROTECTED]> added the comment: When creating your own subclass, you can always inherit from object too to create a new-style class. -- status: pending -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3181] ConfigParsers are classic classes

2008-06-24 Thread Ari Makela
Ari Makela <[EMAIL PROTECTED]> added the comment: New-style classes make object orientated programming considerably more convenient. For example one can use property() instead of __setitem__ et al. There's super(). This is, of course, not a serious problem and one can always implement a composite

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Georg Brandl
Georg Brandl <[EMAIL PROTECTED]> added the comment: Why do you think ConfigParser should be a new-style class? -- nosy: +georg.brandl resolution: -> invalid status: open -> pending ___ Python tracker <[EMAIL PROTECTED]>

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10712/configparser.py ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10711/configparser.diff ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
Changes by Ari Makela <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10711/configparser.diff ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3181] ConfigParsers are classic classes

2008-06-23 Thread Ari Makela
New submission from Ari Makela <[EMAIL PROTECTED]>: The base class, ConfigParser.RawConfigParser does not inherit object and therefore it is a classic class. Test script run with my normal python installation: $ /usr/bin/python -V Python 2.5.2 $ /usr/bin/python arska/configparser.py bar And r