[issue1931] NameError: global name 'basestring' is not defined

2008-01-26 Thread Georg Brandl
Georg Brandl added the comment: I don't see why this shouldn't be closed. -- nosy: +georg.brandl status: pending - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1931 __

[issue1931] NameError: global name 'basestring' is not defined

2008-01-25 Thread Christian Heimes
Christian Heimes added the comment: I've updated the whatsnew docs in r60279. -- nosy: +tiran priority: - low resolution: - invalid status: open - pending __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1931 __

[issue1931] NameError: global name 'basestring' is not defined

2008-01-24 Thread Robert Clark
New submission from Robert Clark: File /home/rclark/lib/src/python/pyparsing/pyparsing-1.3.1/pyparsing.py, line 1511, in __init__ if isinstance( expr, basestring ): NameError: global name 'basestring' is not defined -- messages: 61662 nosy: rclark severity: normal status: open

[issue1931] NameError: global name 'basestring' is not defined

2008-01-24 Thread Robert Clark
Robert Clark added the comment: basestring is in the builtins library for 2.5.1, but is not there in 3.0a2 Linux: RHEL40 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1931 __

[issue1931] NameError: global name 'basestring' is not defined

2008-01-24 Thread Guido van Rossum
Guido van Rossum added the comment: It's been deleted. Use 2to3; it will replace it with 'str'. -- components: +Documentation nosy: +gvanrossum type: compile error - __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1931

[issue1931] NameError: global name 'basestring' is not defined

2008-01-24 Thread Martin v. Löwis
Martin v. Löwis added the comment: Robert, can you please explain why you consider this as a bug? -- nosy: +loewis __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1931 __