-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'GreenStream' object has no attribute 'encoding' #203
Comments
Your guess was correct! This was very similar to #146. I added an encoding attribute to our wrapped |
Works just fine now! Many thanks for the quick fix! |
You're welcome! It is always nice when the solution is so straightforward. That's fairly rare in my experience. 😄 |
I'm currently migrating my CAMP application from Python 2.7 to Python 3.5.3 (on Debian 9) and I now get several tests that fail only when I use green (they pass if I run a
python setup.py test -s tests.generate.test_samples
.See the logs I get below using green. The output intercepted by Green shows that the z3 module (which we depend on) tried to access the 'encoding' attribute of
sys.stdout
By contrast the tests pass when I do not use green:
Looking at the past issues, I guess this somehow similar to Issue #146. As explained, the command
green -a
works as a workaround but it would be nice to be able to capture output :-)Thanks anyway.
The text was updated successfully, but these errors were encountered: