Bug 713591 - pychecker fails on list slice assignment
Summary: pychecker fails on list slice assignment
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pychecker
Version: 15
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 20:47 UTC by Ben Liblit
Modified: 2012-08-07 20:07 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 846855 (view as bug list)
Environment:
Last Closed: 2012-08-07 20:06:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
small test input demonstrating the problem (50 bytes, text/x-python)
2011-06-15 20:47 UTC, Ben Liblit
no flags Details

Description Ben Liblit 2011-06-15 20:47:42 UTC
Created attachment 504941 [details]
small test input demonstrating the problem

Description of problem:

When pychecker encounters code that assigns to a list slice, it fails with an internal error.


Version-Release number of selected component (if applicable):

python-2.7.1-7.fc15.i686
pychecker-0.8.19-2.fc15.noarch


How reproducible:

100% reproducible.


Steps to Reproduce:
1. Save the "problematic.py" attachment found in this bug report.
2. Run "pychecker problematic.py".
  
Actual results:

Diagnostic output reporting an internal error as follows:

    problematic.py:2: INTERNAL ERROR -- STOPPED PROCESSING FUNCTION --
	Traceback (most recent call last):
	  File "/usr/lib/python2.7/site-packages/pychecker/warn.py", line 241,
          in _checkFunction
	    _checkCode(code, codeSource)
	  File "/usr/lib/python2.7/site-packages/pychecker/warn.py", line 154,
          in _checkCode
	    raise NotImplementedError('No DISPATCH member for op %r' % op)
	NotImplementedError: No DISPATCH member for op 43


Expected results:

Warnings if any are appropriate, but certainly not an internal error.

Additional info:

First mentioned as <https://bugzilla.redhat.com/show_bug.cgi?id=658568#c4>.

Comment 1 Vitezslav Crhonek 2011-06-16 11:31:51 UTC
There seems to be identical issue reported to the upstream bug tracker:

http://sourceforge.net/tracker/?func=detail&aid=3208130&group_id=24686&atid=382217

Comment 2 Fedora End Of Life 2012-08-07 20:07:00 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.