On Tue, Mar 12, 2013 at 2:22 PM, Mike Orr <sluggos
...@gmail.com> wrote:
> Interesting that we've just been discussing making a frozen Pylons
> release with all its dependencies because something new has just
> broken. When I deployed an application to a new server and it raised
> an exception, a second exception occurred in WebError and masked the
> first one. It may not be in WebError itself but in
> distribute/setuptools, because the secondary error was "KeyError:
> setuptools". It broke the interactive traceback completely; I just get
> the low-level Paste "Internal Server Error" (in teletype font).
The incompatibility is in WebTest 2.0. Version 1.4.3 works. The next
version 2.0 doesn't, and the current version 2.0.3 doesn't either. I'm
not sure if the problem is in WebTest or Pylons. There's also a
discrepency in WebTest's changelog.
The same behavior occurs in both debug mode (with the interactive
traceback EvalException) and production mode (ErrorMiddleware).
Gael, was there any change in 2.0 that would be likely to throw off
Pylons? Ben, can you trace how Pylons is using WebTest and why it
would matter? There's some interaction between WebError and WebTest I
don't understand.
WebError is at version 0.10.3 in both scenarios, both working and
non-working. The traceback shows the exception occurs in
weberror/formatter.py . But when I downgrade WebTest and keep WebError
the same, the problem goes away. Yet WebError does not depend on
WebTest or import it. And the only occurrence of WebTest I can find in
Pylons is in the tests/__init__.py_tmpl scaffold file. My application
doesn't even have that line ("from webtest import TestApp"); I have
"from paste.fixture import TestApp" instead, which was presumably an
earlier standard. So my application does not even use WebTest at all.
So I don't see how any change in WebTest would affect this error, yet
it does. Maybe there's a problem in WebTest's "egg_info" metadata?
Also, WebTest's CHANGELOG.rst has lost its 1.4.3 section. It appears
in tag 1.4.3 (where the file is called docs/news.txt), but then it was
lost in rev fbf9d45, when the section was renamed to 2.0. So the 2.0
section lists some items that really happened in 1.4.3. Or maybe it
doesn't, if they've been obliterated in the meantime. So in any case,
WebTest's changelog needs to be fixed.
So we need to either adjust Pylons and release a new version, or
determine if it's a bug in WebTest, or release a new version of Pylons
pinned to WebTest==1.4.3.
A colleague I work with has another Pylons application, and it's also
exhibiting the same problem.
--
Mike Orr <sluggos...@gmail.com>
