Installing zope.testrunner on Python 2.4 fails due to a missing
__init__.py in some test subpackage:
Getting distribution for 'zope.testrunner'.
package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not found
(or not a regular file)
error: Setup script exited with error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could someone please remove this release or fix it?
This issue is breaking almost every existing Zope 2 buildout.
Andreas
Marius Gedminas wrote:
Installing zope.testrunner on Python 2.4 fails due to a missing
__init__.py in some test subpackage:
On Thursday, June 10, 2010, Andreas Jung wrote:
Could someone please remove this release or fix it?
This issue is breaking almost every existing Zope 2 buildout.
How can it? Are you not pinning the version of zc.recipe.testrunner and
zope.testing?
I assume the breakage occurs, since I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Richter wrote:
On Thursday, June 10, 2010, Andreas Jung wrote:
Could someone please remove this release or fix it?
This issue is breaking almost every existing Zope 2 buildout.
How can it? Are you not pinning the version of
On Thursday, June 10, 2010, Andreas Jung wrote:
No idea (and I did not investigate it). I had two reports form
co-workers with buildouts breaking suddenly and I encountered a similar
issue with two Plone buildouts.
Could you check which zc.recipe.testrunner version is picked up?
BTW, pinning
On Thu, Jun 10, 2010 at 4:39 PM, Stephan Richter
srich...@cosmos.phy.tufts.edu wrote:
I assume the breakage occurs, since I released zc.recipe.testrunner last night
that uses zope.testrunner instead of zope.testing.
Hhm, the new zc.recipe.testrunner introduces a non-backwards
compatible
On Thursday, June 10, 2010, Hanno Schlichting wrote:
Doing so a in minor release looks bad to me. The release should be a
clear 2.0 and since it depends on a non-final version itself, it
should probably be a beta release on its own.
We are not really changing the API in a BBB incompatible way.
On Thu, Jun 10, 2010 at 5:28 PM, Stephan Richter
srich...@cosmos.phy.tufts.edu wrote:
We are not really changing the API in a BBB incompatible way. We simply
shuffled
code around. We did that all the time and never increased the major version
number.
The code is no longer compatible with
