[issue7688] TypeError: __name__ must be set to a string object

2010-08-02 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: Out of date for Python 2.x, and strings are always unicode objects in 3.x. -- nosy: +georg.brandl resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org

[issue7688] TypeError: __name__ must be set to a string object

2010-07-11 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7688 ___

[issue7688] TypeError: __name__ must be set to a string object

2010-01-13 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- assignee: - jnoller nosy: +jnoller priority: - normal stage: - needs patch type: crash - behavior versions: +Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7688

[issue7688] TypeError: __name__ must be set to a string object

2010-01-12 Thread Frank Millman
New submission from Frank Millman fr...@chagford.com: At the top of my program I have 'from __future__ import unicode_literals'. The relevant lines from my program read - from multiprocessing.managers import BaseManager class MyManager(BaseManager): pass