Warnings in IDLE raise TypeError (such as attempting to import deprecated modules) #48293

Activity

1. craigh commented on Oct 4, 2008

   

   craighmannequin

   on Oct 4, 2008

   MannequinAuthor

   More actions

   In Python 2.6, attempting to import depecated modules in IDLE raises a
   TypeError exception. I verified this with sets, mimify, and MimeWriter.
   Here's the output for sets:

   >> import sets

   Traceback (most recent call last):
     File "<pyshell#2>", line 1, in <module>
       import sets
     File "C:\Python26\Lib\sets.py", line 85, in <module>
       stacklevel=2)
     File "C:\Python26\Lib\warnings.py", line 29, in _show_warning
       file.write(formatwarning(message, category, filename, lineno, line))
   TypeError: idle_formatwarning_subproc() takes exactly 4 arguments (5 given)

   The other modules give a similar trace.

   Normally, I wouldn't consider this a serious issue, but there are some
   major packages out there that still use deprecated modules such as
   these. For example, MySQLdb 1.2.2 and SQLAlchemy 4.7p1 import the sets
   module so they can't be used at all in IDLE.
2. craigh

   added

   topic-IDLE

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   on Oct 4, 2008
3. craigh commented on Oct 4, 2008

   

   craighmannequin

   on Oct 4, 2008

   MannequinAuthor

   More actions

   Actually, it looks like ANY warning will raise this error in IDLE. For
   example:

   >> import warnings
   >> warnings.warn('blah blah')

   Traceback (most recent call last):
     File "<pyshell#5>", line 1, in <module>
       warnings.warn('blah blah')
     File "C:\Python26\Lib\warnings.py", line 29, in _show_warning
       file.write(formatwarning(message, category, filename, lineno, line))
   TypeError: idle_formatwarning_subproc() takes exactly 4 arguments (5 given)
4. craigh

   changed the title [-]Attempting to import deprecated modules in IDLE raises TypeError[/-] [+]Warnings in IDLE raise TypeError (such as attempting to import deprecated modules)[/+] on Oct 4, 2008
5. craigh commented on Oct 5, 2008

   

   craighmannequin

   on Oct 5, 2008

   MannequinAuthor

   More actions

   I should have checked this more carefully, but apparently you can still
   use the imported module after the exception.
6. craigh commented on Oct 5, 2008

   

   craighmannequin

   on Oct 5, 2008

   MannequinAuthor

   More actions

   Okay, I think I've got it now:

   1. If you import sets, it raises TypeError. However, if you import it a
      second time, it seems to work properly.

   2. Trying to import a module that relies on the deprecated module (ie,
      sqlalchemy) fails no matter how many times it's imported.
7. russblau commented on Oct 15, 2008

   

   russblaumannequin

   on Oct 15, 2008

   Mannequin

   More actions

   This error is caused by line 27 in run.py:

       def idle_formatwarning_subproc(message, category, filename, lineno):

   needs to be changed to --

       def idle_formatwarning_subproc(message, category, filename, lineno, 
   line=None):

   so that the function signature matches that of warnings.formatwarning
8. benjaminp commented on Oct 15, 2008

   

   benjaminp

   on Oct 15, 2008

   Contributor

   More actions

   Fixed in r66905.
9. benjaminp

   closed this as completedon Oct 15, 2008
10. ezio-melotti

    transferred this issue fromon Apr 10, 2022