On Sat, Feb 11, 2012 at 11:54 AM, Jonathan Vanasco
jonat...@findmeon.com wrote:
actually, screw that. unit testing for a series of helper wrappers is
too difficult in pylons.
Yes, I've come to that conclusion too. It's one of the main reasons
Pylons 2 switched to Pyramid. It's why I've long
It's the same system virtualenv. it's just that 'using' the package
seems to work fine, but testing it fails.
c is exported in pylons , but that double assignment line seems to not
define it via an import. i guess there's some pylons bootstrap code
that needs to be run.
in any event, based on
actually, screw that. unit testing for a series of helper wrappers is
too difficult in pylons. pyramid and 'core' usage gets covered.
pylons doesn't. now i'm going to brunch!
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this
my tests keep failing on pylons packages. actually, i can't even run
the tests.
i've traced the error to this being in my packages:
from pylons import c
works fine in production, but not in testing
looking at pylons/__init__.py, i see this line:
tmpl_context = c =
You might want to ensure both systems are running the same version of
Pylons. I believe c is deprecated in 0.10 and removed entirely in 1.0 in
favor of tmpl_context.
On Sat, Feb 11, 2012 at 12:06 AM, Jonathan Vanasco jonat...@findmeon.comwrote:
my tests keep failing on pylons packages.
