pychecker crashes with python2.7

Bug #692945 reported by أحمد المحمودي (Ahmed El-Mahmoudy)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyChecker
Unknown
Unknown
pychecker (Debian)
Fix Released
Unknown
pychecker (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: pychecker

Please have a look at this FTBFS in natty:
http://launchpadlibrarian.net/61007900/buildlog_ubuntu-natty-i386.git-buildpackage_0.5.12_FAILEDTOBUILD.txt.gz

the build fails at:
PYTHONPATH=. pychecker -e Error -q git-buildpackage
Processing module git-buildpackage (git-buildpackage)...
  Caught exception importing module git-buildpackage:
    File "/usr/lib/pymodules/python2.7/pychecker/checker.py", line 680, in _initModule()
      self.addClass(tokenName)
    File "/usr/lib/pymodules/python2.7/pychecker/checker.py", line 592, in addClass()
      self.__addAttributes(c, c.classObject)
    File "/usr/lib/pymodules/python2.7/pychecker/checker.py", line 579, in __addAttributes()
      c.addMembers(classObject)
    File "/usr/lib/pymodules/python2.7/pychecker/checker.py", line 391, in addMembers()
      self.addMembersFromMethod(method.im_func)
    File "/usr/lib/pymodules/python2.7/pychecker/checker.py", line 407, in addMembersFromMethod()
      operand = OP.getOperand(op, func_code, oparg)
    File "/usr/lib/pymodules/python2.7/pychecker/OP.py", line 66, in getOperand()
      return func_code.co_names[oparg]
  IndexError: tuple index out of range

Tags: python27
Barry Warsaw (barry)
tags: added: python27
Revision history for this message
Barry Warsaw (barry) wrote :

Note that there does not seem to be a newer upstream pychecker release that fixes this. Because Python 2.7 support seems spread out among several CVS commits, I tried doing a merge package from the latest CVS tree, but there were conflicts. I think we should wait until a new upstream is released, and/or a new version hits Debian. The resolution of disabling pychecker when used with 2.7 (see git-buildpackage 0.5.13ubuntu1) seems right to me for now.

Changed in pychecker (Ubuntu):
status: New → Triaged
Revision history for this message
Barry Warsaw (barry) wrote :

Please use this bug report to list packages where pychecker has been disabled for Python 2.7. When pychecker is finally fixed, I'll go back around and re-enable the checks.

git-buildpackage

Changed in pychecker (Debian):
status: Unknown → Confirmed
Changed in pychecker (Debian):
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pychecker - 0.8.19-1

---------------
pychecker (0.8.19-1) unstable; urgency=low

  * New upstream release.
    - This code is now compatible with Python 2.7 (closes: #609438)
  * Bump Standards-Version to 3.9.1.0 (no packaging changes).
  * Rewrite debian/regression.sh to handle the new upstream unit tests.
  * Update debian/copyright to reference Thomas Vander Stichele.
  * Update debian/pychecker.1 manpage to update the package version.
  * Update debian/README.Debian to clarify the status of pychecker2.
  * Update debian/patches/remove-shebang.patch to match upstream code.
  * Add new patch fix-version.patch so pychecker reports the right version.
  * Add new patch remove-bashisms.patch so test_check.sh runs with dash.
  * Add new patch put-back-missing-files-from-cvs.patch.
    - This patch adds back a *huge* number of files that were mistakenly
      not included in the official upstream 0.8.19 tarball. These files
      will be included in the 0.8.20 release, using a new MANIFEST.in
      which I provided. However, for the time being upstream has asked
      me to deal with this problem by patching the Debian package. All
      of the extra files that I have included in my 0.8.19-1 release were
      pulled directly from upstream CVS using 'cvs co -r v0_8_19'.
 -- ALEFHAHMEEMDAL ALEFLAMMEEMHAHMEEMWAWDALYEH (Ahmed El-Mahmoudy) <email address hidden> Sun, 23 Jan 2011 19:47:08 -0600

Changed in pychecker (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.