Dan Hemberger

> Most people who want to use MechanicalSoup are already using it. I don't think anyone is holding it's breath until the 1.0 release. I was originally going to concede...

First and foremost: I believe this can be done without breaking backwards compatibility. That said, I think the motivations for making this change are sufficiently important that it is worth...

I agree, there's definitely not an obvious answer here. As you noted, in some places it is important to use `self.form`, but in others it's redundant (or even incorrect, e.g....

Hi, thanks for your interest in MechanicalSoup! I believe the issue is that you called the base class method `submit` instead of the preferred method `submit_selected`. That is, instead of...

Thanks for your interest in MechanicalSoup! You should be able to select the form based only on the class attribute, assuming you can construct a unique selector. It would look...

It looks like dryscrape is no longer actively maintained as of 2017, so I think we'd probably want to avoid officially supporting it. However, if you get it working, please...

Thanks for the heads up! I assume we would then remove `python setup.py test` as an entrypoint into running the tests, and just rely on invoking `pytest`; that is, I...

Both ideas seem to reasonably solve the problem without a loss of efficiency, which is great! Push/pop adds more cruft to user code ``` br.push_history() br.follow_link(link) br.pop_history() ``` but is...

Another possibility (one that I don't necessarily like, but would stay more-or-less consistent with mechanize and RB) is to implement the history as a deque, whose size you could configure...

Thanks for your question, and sorry for the delayed response! While the response is not stored in the browser state, it is returned by all methods that produce one. Is...