Opened 13 years ago

Closed 9 years ago

#4413 closed defect (duplicate)

'?' in docstring gets interpreted immediately by the parser

Reported by: justin Owned by: mhansen
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: user interface Keywords:
Cc: Merged in:
Authors: Reviewers: Keshav Kini
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: #12719 Stopgaps:

Status badges

Description

The following code, entered in the command-line interface to Sage, shows the effect: 

sage: def foo(x):
   ....:     '''
   ....:     Eh?
Object `Eh` not found.
   ....:     '''
   ....:     return x
   ....:

The parser appears to act on the '?' right away, rather than wait for the end of the thing being defined (or realizing that '?' in this case is not to be acted on).

The effect shows up with both single- and double- quotes, and with and without the "raw" qualifier (r''').

This may be related to Trac#4405.

Change History (7)

comment:1 Changed 13 years ago by mhansen

  • Owner changed from was to mhansen
  • Status changed from new to assigned

This is not related to #4405. In fact, it is an IPython bug. I've reported it here: ​http://lists.ipython.scipy.org/pipermail/ipython-dev/2009-January/004812.html

comment:2 Changed 10 years ago by mhansen

  • Report Upstream set to N/A

This is fixed in IPython 0.12. We should close this when #12719 gets closed.

Last edited 10 years ago by mhansen (previous) (diff)

comment:3 Changed 10 years ago by kini

  • Dependencies set to #12719
  • Status changed from new to needs_review

comment:4 Changed 10 years ago by kini

  • Status changed from needs_review to positive_review

comment:5 Changed 10 years ago by jdemeyer

  • Milestone changed from sage-5.0 to sage-pending

comment:6 Changed 10 years ago by jdemeyer

  • Milestone changed from sage-pending to sage-duplicate/invalid/wontfix

comment:7 Changed 9 years ago by jdemeyer

  • Resolution set to duplicate
  • Reviewers set to Keshav Kini
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.