Implements suggestion from this issue: https://github.com/olzhasar/pytest-watcher/issues/11

The commits are rather dirty, please let me know if I should squash them.

I only tested locally with Python 3.10 with the following parameters (using pip install -e .)

ptw .
ptw . --now
ptw . --now --entrypoint tox
ptw . --entrypoint tox

The issue appears when performing a file move operation from not watched to a watched destination.

Expected behaviour: if destination file path in move operation appears to be watched (while source file path is not), pytest-watcher should trigger pytest.

Here is an example of events appearing when using unison tool, which is syncing changes to remote destination by first creating a temporary file and then renaming it to a destination:

2022-10-17 15:32:18 - Created file: ./tests/sites/.unison.test_discover.py.7f0384dc585055b3fcfb405908d8de58.unison.tmp
2022-10-17 15:32:18 - Modified directory: ./tests/sites
2022-10-17 15:32:18 - Modified file: ./tests/sites/.unison.test_discover.py.7f0384dc585055b3fcfb405908d8de58.unison.tmp
2022-10-17 15:32:18 - Modified directory: ./tests/sites
2022-10-17 15:32:18 - Modified file: ./tests/sites/.unison.test_discover.py.7f0384dc585055b3fcfb405908d8de58.unison.tmp
2022-10-17 15:32:18 - Moved file: from ./tests/sites/.unison.test_discover.py.7f0384dc585055b3fcfb405908d8de58.unison.tmp to ./tests/sites/test_discover.py
2022-10-17 15:32:18 - Modified directory: ./tests/sites

These events gathered with watchdog example code here: https://pypi.org/project/watchdog/

The fix seems to be pretty straightforward - just extend the condition in process_event method to something like this:

    def process_event(self, event: events.FileSystemEvent) -> None:
        if _is_path_watched(event.src_path):
            emit_trigger()
        elif event.event_type == events.EVENT_TYPE_MOVED and _is_path_watched(event.dest_path):
            emit_trigger()

Thank you for the project

#1

It'd be nice to have an option / flag for this. I am duplicating running the tests automatically by having to write 2 commands with the same files listed (one for py.test, one for ptw)

Is it possible we can have a changelog file to see releases over time w/o GitHub releases?

The reason why is I think changelog files are the easier way to see changes. I feel GitHub releases adds distractions/walls/barriers that make it more frustrating to catch up with the changes 😄

Python 3.10 was released on 2021-10-04:

• https://discuss.python.org/t/python-3-10-0-is-now-available/10955

$ tox -e py310
.package create: /private/tmp/pytest-watcher/.tox/.package
.package installdeps: poetry-core>=1.0.0
py310 create: /private/tmp/pytest-watcher/.tox/py310
py310 installdeps: watchdog, pytest, pytest-mock, freezegun
py310 inst: /private/tmp/pytest-watcher/.tox/.tmp/package/1/pytest-watcher-0.2.1.tar.gz
py310 installed: attrs==21.2.0,freezegun==1.1.0,iniconfig==1.1.1,packaging==21.3,pluggy==1.0.0,py==1.11.0,pyparsing==3.0.6,pytest==6.2.5,pytest-mock==3.6.1,pytest-watcher @ file:///private/tmp/pytest-watcher/.tox/.tmp/package/1/pytest-watcher-0.2.1.tar.gz,python-dateutil==2.8.2,six==1.16.0,toml==0.10.2,watchdog==2.1.6
py310 run-test-pre: PYTHONHASHSEED='546577221'
py310 run-test: commands[0] | pytest
========================================================== test session starts ===========================================================
platform darwin -- Python 3.10.1, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
cachedir: .tox/py310/.pytest_cache
rootdir: /private/tmp/pytest-watcher
plugins: mock-3.6.1
collected 21 items

tests/test_pytest_watcher.py .....................                                                                                 [100%]

=========================================================== 21 passed in 0.75s ===========================================================
________________________________________________________________ summary _________________________________________________________________
  py310: commands succeeded
  congratulations :)

Would you consider making pytest-watcher run right away rather than waiting for changes?

I find that I often end up adding and deleting lines to trigger the first run

Hi, this looks like an interesting package, I've tested it locally on a stub project and it seems to work fine, nice work.

However, I've worked with real projects that are tied to other tooling besides pytest, for instance, tox, make or even just bash scripts (which in turn, execute pytest with a particular setup).

A really useful feature IMO would be to add an argument to the CLI, to override your entry point executable, so we can hook the watcher with other executables (though, I guess that partially defeats the purpose of naming this package pytest-watcher 😄 ).

What are your thoughts on it? Worth implementing? I'd be happy to work on a PR for this if you agree with it.

Hi! Thanks for forking ptw and continuing it! Since you've released pytest–watcher on pypi, automatic workflows are now picking your package over the old one, which is mostly great. Unfortunately, ptw could previously be run on the present working directory by calling ptw without options. The new version breaks this backward compatibility. Unless you have very good reason to do, I suggest you re-introduce this behaviour.

So that clicking them takes you to PyPI and the license instead of just badge images.

Preview:

https://github.com/hugovk/pytest-watcher/blob/011962f6712170c4128d79b62a997adc4b5a1777/README.md

Hello!

Thank you very much for the simple and working pytest-watcher solution!

I've missed a little functionality about filtering watch files above *.py. Because in my projects also .env and .ini files can widely change the behaviour.

I added arguments to the command line now. In my case, it is okay as it. In future, we can also put some of these --include-filter and --ignore-filter arguments to the configuration file.

And I also have small doubts about confusing examples. But for now, I have no idea how to make it more clear except documentation remark. https://github.com/olzhasar/pytest-watcher/compare/master...aptakhin:pytest-watcher:add-other-extensions-support#diff-58fb153a128d801a5a58c94d9fcd912af6349faa66d202cc43ec4e1c23ae25dfR54-R62

Hello @olzhasar. First of all, thanks for your contribution, its really handy.

I'd suggest a little modification at the function

def _run_pytest(args) -> None:
    subprocess.run(["pytest", *args])

To something like

def _run_pytest(args, clear=False) -> None:
    if clear:
        subprocess.run(["clear"])
    subprocess.run(["pytest", *args])

To clear the results before each test.

Thanks!!