Code

Opened 17 months ago

Closed 17 months ago

Last modified 4 months ago

#19789 closed Bug (invalid)

With IPython `./manage.py shell` gives back a DeprecationWarning regarding the with statement

Reported by: crodjer Owned by: nobody
Component: Core (Management commands) Version: master
Severity: Normal Keywords:
Cc: int_ua Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I came across this issue while debugging #19738. This happens in a fresh django project.

The traceback:

└─> ./manage.py shell                                                                                                                          Python 2.7.3rc2 (default, Mar 21 2012, 06:59:11) 
Type "copyright", "credits" or "license" for more information.

IPython 0.13.1 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.
('VIRTUAL_ENV ->', '/home/rohan/.virtualenvs/django/lib/python2.7/site-packages')
/home/rohan/workspace/src/ipython/IPython/frontend/terminal/interactiveshell.py:463: DeprecationWarning: With-statements now directly support multiple context managers
  with nested(self.builtin_trap, self.display_trap):

It doesn't seem like an issue in IPython because I was able to similarly invoke it from a python script without any warning.

Attachments (0)

Change History (6)

comment:1 Changed 17 months ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Deprecation warnings are silent in Python by default, but Django makes them loud since #18985 was fixed.

comment:2 Changed 17 months ago by crodjer

Alright, thanks. This is an IPython issue then. Should I close this as invalid? Also, if #19737 goes along, all the similar issue will become irrelevant.

comment:3 Changed 17 months ago by crodjer

  • Resolution set to invalid
  • Status changed from new to closed

comment:4 Changed 11 months ago by anonymous

Any work around this thing, the warning is pretty irritating and I am finicky about these things

comment:5 Changed 8 months ago by int_ua

  • Cc int_ua added

The workaround/fix is to remove the nested() function:

with self.builtin_trap, self.display_trap:

https://github.com/ipython/ipython/issues/4455

comment:6 Changed 4 months ago by claudep

Note that this should be fixed by [0c6a3399523d850cfbd20de54cd089419a47383d]

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.