--pdb behavior

[max-sixty]

I think:

• ptw --pdb -- [pytest args] waits for pdb to exit before re-running the tests
• ptw -- --pdb restarts the test on any change, even if you're in the middle of debugging

Is that correct?

I actually find it v helpful - the second is useful if you always want a debugger ready to go with the latest as soon as you need one. But not sure that's consistent with #64?

If so, we could make that explicit - I only discovered by accident

[max-sixty]

This seems to have reverted to the first behavior in 4.2.0, which is a shame. Is there any way to get the second?

[max-sixty]

Would you take a PR reverting to the old behavior, with the above added as instructions?

That way people can choose either option - if pdb is a ptw arg, then it'll wait on changes; if pdb is a pytest arg, it'll restart on changes as it generally does