[Bug 106960] Re: Python 2.5 testing issues

Sebastian Ramacher 106960 at bugs.launchpad.net
Tue Feb 11 10:06:54 UTC 2014


Is this still an issue?

** Changed in: codespeak-lib (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to codespeak-lib in Ubuntu.
https://bugs.launchpad.net/bugs/106960

Title:
  Python 2.5 testing issues

Status in “codespeak-lib” package in Ubuntu:
  Incomplete

Bug description:
  There seems to be a library/executable mismatch in the py.test suite
  I'm currently using in Edgy. I'm not sure if it's an Ubuntu-specific
  bug or it should be reported upstream as well.

  I want to test some software of mine, which employs the py.test suite,
  using the py.test script. If I just start it, it's all right, but it
  uses the 2.4 interpreter even though my test scripts have the
  #!/usr/bin/python2.5 correctly set.

  If I try forcing the interpreter this way:

  py.test --exec=/usr/bin/python2.5

  Traceback (most recent call last):
    File "/usr/bin/py.test", line 4, in ?
      py.test.cmdline.main() 
    File "/usr/lib/python2.4/site-packages/py/test/cmdline.py", line 17, in main
      failures = session.main(args)
    File "/usr/lib/python2.4/site-packages/py/test/terminal/terminal.py", line 32, in main
      return remote.main(self.config, self._file, self.config._origargs)
    File "/usr/lib/python2.4/site-packages/py/test/terminal/remote.py", line 140, 
  [... omissis ...]

  It just seems it's trying to use the 2.4 library with the 2.5
  interpreter.

  The solution seems pretty simple. I just created a 'new' py25.test
  file in my bin directory, identical to the py.test file but sporting a
  #!/usr/bin/python2.5 shell bang, and everything works fine.

  If support for both python 2.4 and 2.5 is needed, we should either
  create a different testfile for each interpreter version (e.g.
  py24.test, py25.test ... ) or the py.test should be rewritten in order
  to handle the --exec call correctly, by launching a new interpreter if
  it's different from the one the py.test script has been invoked with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/codespeak-lib/+bug/106960/+subscriptions



More information about the foundations-bugs mailing list