Consider moving project to pytest-dev for maintenance

[amitSA]

I appreciate this project (and it looks like others do to), and I can't find any other existing project that does thread based parallelism.

However it seems like it's becoming un-mantained, would the owners consider moving this to the pytest-dev organization ? There are some low-hanging fruit that others have PRs for and I'd love to see those merged!

I could also help out with that effort.

[ssbarnea]

That was a good call, I ended up avoiding any plugin that is now under pytest-dev in order to not rely of something that can easily become a maintenance liability. It is quite easy to initiate the process with a ticket on https://github.com/pytest-dev/meta/issues?q=is%3Aissue+

[amitSA]

@kevlened I think you're the maintainer, so this will need your approval.

[r2dev2]

For Python 3.9 support, I have uploaded @andni233's fork to pip under the name of pytest-parallel-39 if anyone wants to use this module with Python 3.9.

[ssbarnea]

@kevlened Any answer would be better than none.

[kevlened]

@amitSA Thanks for the suggestion. Adoption is the best outcome for pytest-parallel. While the promise of threaded testing is appealing, the implementation relies upon Pytest internals which requires an up-to-date understanding for each Pytest version. It also relies on Python's multiprocessing lib which seems to have nuances between versions. These challenges make pytest-parallel tricky to maintain.

I'm grateful for @andni233's contribution. It's been merged, although attempting to deploy to PyPI has surfaced its own issues on my m1. You're welcome to use @r2dev2's upload or attempt to install directly from this repo. Otherwise, I hope it will be adopted soon.

If @ssbarnea or @amitSA would like to manage the adoption process, let me know, and I'll add you as a contributor to the project.

[amitSA]

Sure, if you add me as a contributor I can manage the adoption process to pytest-dev. Thanks @kevlened!

Looking at the instructions for migrating to pytest-dev, the first step is to transfer repo ownership to a pytest-dev admin. In order for I to do that, I'll need to be an admin.

[kevlened]

Excellent! Invited you to be an admin.

[amitSA]

@kevlened I've been preoccupied so haven't been able to start the process, maybe @ssbarnea you'd like to start the migration assuming @kevlened is okay with it ?

[azmeuk]

@amitSA I volunteer to start the process if everyone is ok with that.

[amitSA]

Fine by me. @kevlened are you okay with that ? (Asking since they are the original owner)

[azmeuk]

I just sent the submission to the pytest-dev list.

[kevlened]

Excellent @azmeuk and @amitSA, sorry for the radio silence. If there's access you need for the transfer, I'm happy to help.

[azmeuk]

@amitSA @kevlened @ssbarnea @r2dev2 If one of you had already made a contribution to pytest-dev, please ack for the submission of pytest-parallel by replying in the mail thread. There is only one ack missing!

[azmeuk]

Hi everyone. Bad news.

In the pytest-dev mailing list Ronny Pfannschmidt is opposed to the migration of pytest-parallel to pytest-dev until there has been some code cleanups and refactoring.

The situation seems blocked, since I guess @kevlened won't have time to spend on this.

The only solution I can think of is that @kevlened give write access to this repository to people who can make the cleanups, and the we can follow the migration process.

What do you think?

[azmeuk]

@kevlened gentle ping. Would you consider giving admin rights to @amitSA and myself for github and pypi so we could at least do the minimal project maintenance? 🙏

[kevlened]

Hi @azmeuk. You've been added as an admin to both github and pypi. I really appreciate your help.

[azmeuk]

Thank you very much. I just released v0.1.1 with python 3.9 support.

I am closing this one as I just opened another issue for maintainers search.