Jorgen Schäfer

> No, really, this is nonsense. rope is not expected to fix broken code, and I don't want to make it into corrector of one. Thank you for the clarification....

There was some prior discussion about assess in #37. Basically, I'd be happy to use assess for buttercup instead of what buttercup uses internally. I'm not sure how this would...

As described in #49, another advantage here would be that we can tell various sources of errors apart, and report them correctly, e.g. when there are errors both in before/after...

Thank you for the suggestion. A link to http://docs.python-guide.org/en/latest/dev/virtualenvs/ would indeed be useful there! :-)

Hm. Yeah. Maybe a bit more verbose in the README – it really is as simple as `M-x pyvenv-workon RET yourenv RET`, though :-)

`workon` is a name from virtualenvwrapper. Elpy does not intend to install a full Python environment on your system, it uses your Python environment. (E.g. Elpy does not come with...

Yes, it would be.

Sounds awesome, thank you!

Hello, and thanks for the suggestion. Currently, this is not possible in buttercup (short of wrapping `(when (server-available) ...)` around all bodies). While I can relate to the idea of...

Hm. I still believe that tests should be independent. It might work to have a `before-each` clause that does `(signal 'buttercup-pending "SKIPPED")` if a condition is not met. Either that,...