Consider moving under pytest-dev?

[nicoddemus]

Hi,

Would you like to move the plugin under the pytest-dev org? The idea of such a move is just to increase the visibility of the plugin and eventually share maintenance, but as the original author you still retain full control over the implementation and oversee of the plugin. You can read more in Submitting plugins to pytest-dev.

Cheers!

[micuda]

Hi @joeyespo, did you consider this suggestion? There are some cool features, e.g. #117 and #110 (for me), waiting for merge. Thank you for this great library. =)

[stuaxo]

Hi @joeyespo if you've moved on then pytest-dev is a really good suggestion, from the link above:

Lots of people seem to be using this, but it's fair enough if you don't want to maintain this, it certainly can be a burden - it would be a shame for something so useful to languish.

[sotte]

Hello @joeyespo, I'm a big fan of pytest-watch and use it on a daily basis (actually used, because do to the poetry incompatibility I can't use it anymore #112). It would be a shame if the plugin just died. There is still quite the interest in the plugin and even active contributions. Moving it to the pytest-dev organization like @nicoddemus suggested really sounds like a good solution. @joeyespo you don't have to maintain it anymore and the contributions can be integrated.

[meshantz]

The license on this is MIT. Has anyone forked this and updated it to meet the acceptance requirements for pytest-dev?

That should be enough to get it in there and then all of the outstanding work requested here could be retargeted there...

[sotte]

There is pytest-watcher which does basically the same as pytest-watch.
https://github.com/olzhasar/pytest-watcher

What about pytest-watch?
pytest-watch was around for a long time and was solving exactly this problem. Sadly, pytest-watch is not maintained anymore and not working for many users. I wrote this tool as a substitute
-- https://github.com/olzhasar/pytest-watcher#what-about-pytest-watch