Ubuntu
pytables package

pytables FTBFS with python3.5

Bug #1478146 reported by Steve Langasek
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pytables (Debian)
Fix Released
Unknown
pytables (Ubuntu)
Fix Released
High
Barry Warsaw
Wily
Fix Released
High
Barry Warsaw

Bug Description

pytables fails to build during its build-time test suite with python3.5. The failure is:

======================================================================
ERROR: None (tables.tests.test_types.RangeTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
ValueError: could not convert string to float: '124c'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/vorlon/devel/canonical/python3.5/pytables-3.1.1/build/lib.linux-x8
6_64-3.5/tables/tests/test_types.py", line 104, in test01_type
    rec['var4'] = "124c"
  File "tables/tableextension.pyx", line 1583, in tables.tableextension.Row.__setitem__ (tables/tableextension.c:16156)
SystemError: <class 'TypeError'> returned a result with an error set

----------------------------------------------------------------------

I don't know what to make of this failure, since the traceback explicitly mentions TypeError, the test is meant to catch a TypeError, and nowhere do we see the error message that we should see if a different exception was thrown ("expected a TypeError").

Revision history for this message
Steve Langasek (vorlon) wrote :

Full build log available at: https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+build/7558672

Changed in pytables (Ubuntu Wily):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Julian Taylor (jtaylor) wrote :

its an issue in the c-extension, setting an exception and not returning NULL. Likely an issue in cython which might not be python3.5 compatible yet.

Revision history for this message
Barry Warsaw (barry) wrote :

There were other problems locally built against the py35asdefault PPA, so I'm updating the package to the latest upstream, 3.2.1. That version fixes those problems (although it has a locale bug[1]) and now I'm back to the above failure. I will be looking into that today, so watch the PPA first.

[1] https://github.com/PyTables/PyTables/issues/485

Changed in pytables (Ubuntu Wily):
status: Triaged → In Progress
assignee: nobody → Barry Warsaw (barry)
Revision history for this message
Barry Warsaw (barry) wrote :

If it is a cython issue, I wonder if 0.23 fixes it?

Revision history for this message
Barry Warsaw (barry) wrote :

It's not a cython issue, it's a bug in PyTables. I think I have a fix so I'll report this upstream and work on a wily package update (and will send a debdiff to Debian BTS).

Bug Watch Updater (bug-watch-updater)
Changed in pytables (Debian):
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in pytables (Debian):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pytables - 3.2.1-0ubuntu1

---------------
pytables (3.2.1-0ubuntu1) wily; urgency=medium

  * New upstream release.
  * Fixes Python 3.5 support. (LP: #1478146)
  * Quilt patches updated:
    - Deleted:
      + 0003-Better-control-of-verbosity-in-unittests.patch
      + 0006-fix-an-import-issue-with-cython-newer-than-0.20.2.patch
      + 0007-Temporay-desable-tests-that-use-the-lz4-conpressor.patch
    - Refreshed:
      + 0001-use-dynamic-lib.patch
      + 0002-Use-system-compression-libs.patch
      + 0004-Never-use-the-msse2-flag-explicitly.patch
      + 0005-Do-not-fetch-icons-for-external-web-sites.patch
   * debian/control:
     - Add to Build-Depends: python{,3}-setuptools, locales
     - Bump Standards-Version to 3.9.6.
   * debian/rules: Run the test suites under en_US.UTF-8 locale.
   * debian/python-tables{,-doc}.docs: It's README.rst now.

 -- Barry Warsaw <email address hidden> Tue, 11 Aug 2015 18:11:30 -0400

Changed in pytables (Ubuntu Wily):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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