this is exactly the case i wanted to eliminate by pushing the pytest-dev I would ask the author to move it under pytest-dev (and add pypi access as well) and then we can properly maintain it? For github, it requires adding him to the pytest-dev team upfront
On 3 March 2015 at 06:41, meejah <issues-re...@bitbucket.org> wrote: > New issue 691: move pytest-twisted plugin to pytest organization > > https://bitbucket.org/pytest-dev/pytest/issue/691/move-pytest-twisted-plugin-to-pytest > > meejah: > > As per a possible-bug I recently filed against the pytest-twisted plugin, > it seem its author no longer wishes to maintain it. More details: > > https://github.com/schmir/pytest-twisted/issues/4 > > It would be a shame to see it languish, as it has worked for me with > Twisted code I've tried it against -- and luckily isn't very much code. > Hopefully, pytest can move it to their own organization/repositories etc. > > > _______________________________________________ > pytest-commit mailing list > pytest-commit@python.org > https://mail.python.org/mailman/listinfo/pytest-commit > -- Anatoly Bubenkov
_______________________________________________ pytest-commit mailing list pytest-commit@python.org https://mail.python.org/mailman/listinfo/pytest-commit
