0.9.17 won't install

Bug #1068498 reported by Doug Winter
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
testtools
Fix Released
Critical
Jonathan Lange

Bug Description

ImportError: No module named matchers._impl

I don't get this error with 0.9.16

Revision history for this message
Jonathan Lange (jml) wrote :

Thanks for the bug report both!

I've rolled a new release 0.9.18 that I *think* addresses the problem. I'd much appreciate it if you could download it and check it out.

cheers,
jml

Changed in testtools:
status: New → Fix Committed
importance: Undecided → Critical
assignee: nobody → Jonathan Lange (jml)
Revision history for this message
Michel Lind (michel-slm) wrote :

Seems fine on Python 2.7 -- I'm updating the Fedora package right now -- but on Python 3.3, which the NEWS says is supported modulo some cosmetic error, it does not actually work:

Bytecompiling .py files below /builddir/build/BUILDROOT/python-testtools-0.9.18-1.fc18.noarch/usr/lib/python3.3/ using /usr/bin/python3.3
*** Error compiling '/builddir/build/BUILDROOT/python-testtools-0.9.18-1.fc18.noarch/usr/lib/python3.3/site-packages/testtools/_compat2x.py'...
  File "/usr/lib/python3.3/site-packages/testtools/_compat2x.py", line 16
    raise exc_class, exc_obj, exc_tb
                   ^
SyntaxError: invalid syntax

Should I file a separate bug for this?

Revision history for this message
Michel Lind (michel-slm) wrote :

Oops, spoke too soon -- tests fail on Python 2.7 as well:
+ /usr/bin/python setup.py test
running test
Traceback (most recent call last):
  File "setup.py", line 81, in <module>
    cmdclass={'test': testtools.TestCommand})
  File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
    dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/builddir/build/BUILD/testtools-0.9.18/testtools/distutilscmd.py", line 62, in run
    exit=False)
  File "/builddir/build/BUILD/testtools-0.9.18/testtools/run.py", line 155, in __init__
    self.parseArgs(argv)
  File "/builddir/build/BUILD/testtools-0.9.18/testtools/run.py", line 232, in parseArgs
    self.createTests()
  File "/builddir/build/BUILD/testtools-0.9.18/testtools/run.py", line 241, in createTests
    self.module)
  File "/usr/lib/python2.7/unittest/loader.py", line 128, in loadTestsFromNames
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib/python2.7/unittest/loader.py", line 113, in loadTestsFromName
    test = obj()
  File "/builddir/build/BUILD/testtools-0.9.18/testtools/tests/__init__.py", line 9, in test_suite
    from testtools.tests import (
ImportError: cannot import name matchers

Revision history for this message
Doug Winter (doug-isotoma) wrote :

Installs for me on Ubuntu Lucid, although I get some warnings:

warning: no files found matching 'HACKING'
warning: no files found matching 'MANUAL'

Our test suite runs too.

Revision history for this message
Jonathan Lange (jml) wrote :

Michel, please file a separate bug for the Python 3 compat thing. I'm intrigued by it, since I don't think we've changed anything around that.

I've addressed the test failures with the 0.9.18 release. http://static.mumak.net/testtools-0.9.19-r281.tar.gz is a candidate release tarball. I'll hold off on releasing until we decide what to do about the Python 3.3 thing. I'd appreciate it if you could verify that it works.

Revision history for this message
Michel Lind (michel-slm) wrote :

OK, the Python 3.3 issue is probably related to the issue affecting Python 2.7 as well. With the snapshot, the only test failures with Python 3.3 are the cosmetic ones mentioned in NEWS -- dictionary ordering changes, as well as strings containing null bytes

Revision history for this message
Jonathan Lange (jml) wrote : Re: [Bug 1068498] Re: 0.9.17 won't install

On 19 October 2012 12:59, Michel Alexandre Salim
<email address hidden> wrote:
> OK, the Python 3.3 issue is probably related to the issue affecting
> Python 2.7 as well. With the snapshot, the only test failures with
> Python 3.3 are the cosmetic ones mentioned in NEWS -- dictionary
> ordering changes, as well as strings containing null bytes

Sweet. I guess I'll fix those up too, and then roll out 0.9.19. Sorry
about the noise!

jml

Revision history for this message
Jonathan Lange (jml) wrote :

On 19 October 2012 13:09, Jonathan Lange <email address hidden> wrote:
> On 19 October 2012 12:59, Michel Alexandre Salim
> <email address hidden> wrote:
>> OK, the Python 3.3 issue is probably related to the issue affecting
>> Python 2.7 as well. With the snapshot, the only test failures with
>> Python 3.3 are the cosmetic ones mentioned in NEWS -- dictionary
>> ordering changes, as well as strings containing null bytes
>
> Sweet. I guess I'll fix those up too, and then roll out 0.9.19. Sorry
> about the noise!

Done.

Give 0.9.19 a try.
http://pypi.python.org/packages/source/t/testtools/testtools-0.9.19.tar.gz#md5=1c02b1ff56424a0f80f6dda0afc456c8

Changed in testtools:
milestone: none → next
status: Fix Committed → Fix Released
Revision history for this message
Michel Lind (michel-slm) wrote :

Works fine -- as it turns out, there is indeed a Python 3 issue with the way testtools handle compatibility libraries and how we build our Python packages in Fedora; opening a separate bug for it as there is an oddity in the way compat.py is written as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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