After the successful transfer of pytest-order (thank you for that smooth
experience!), I have been thinking about the transfer of another library
- pyfakefs - where I am a contributor. I have been discussing this with
the package maintainer, John McGehee, who is also in favor for this, and
decided to first ask here if that is feasible.
pyfakefs (https://github.com/jmcgeheeiv/pyfakefs) is a library that
mocks the file system. It has originally been developed by Mike Bland at
Google, later transferred to GitHub (after the shutdown of Google Code
in 2011), where John McGehee has forked it, added direct support for
unittest and doctest, and has maintained it since then (with my help
since a few years ago). Later a contributor added support for pytest via
the fs fixture, with more support for pytest following eventually. Today
the fs fixture is probably the main means to access pyfakefs, judging by
the issues and the dependent repositories.
So, while pyfakefs is not a pure pytest plugin, and it doesn't follow
the naming convention pytest-xx, we thought that it would be a good idea
to transfer it to pytest-dev, with the following goals:
- ensure continued maintenance
- increase compatibility with pytest and pytest-plugins
- improve visibility of the package, especially for pytest developers
- ideally, benefit from the larger community to get more code reviews
and issue reports
For reference see also https://github.com/jmcgeheeiv/pyfakefs/issues/590
What do you think? Thanks!
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
On Sep 17 @ 12:00, pytest-dev-request(a)python.org wrote:
> Send pytest-dev mailing list submissions to
> pytest-dev(a)python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/pytest-dev
> or, via email, send a message with subject or body 'help' to
> pytest-dev-request(a)python.org
>
> You can reach the person managing the list at
> pytest-dev-owner(a)python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pytest-dev digest..."
>
>
> Today's Topics:
>
> 1. Fwd: [pytest-otel] OpenTelemetry plugin for pytest (kuisathaverat)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 17 Sep 2021 10:43:30 +0200
> From: kuisathaverat <kuisathaverat(a)gmail.com>
> To: pytest-dev(a)python.org
> Cc: observability-robots(a)elastic.co, cyrille.leclerc(a)elastic.co
> Subject: [pytest-dev] Fwd: [pytest-otel] OpenTelemetry plugin for
> pytest
> Message-ID:
> <CAKo5QrpCt6R_KHL9uTpYnSPcSo4HBkVCK3B+5oSoWqvGBsmoTw(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Dear community,
>
> We have developed an OpenTelemetry plugin for pytest, this plugin
> sends test results
> as
> distributed traces with OpenTelemetry. We want to make this plugin
> available on the official pytest
> repository and allow the community to improve it.
> If there is interest to have it on the pytest-dev repository, I will
> accomplish all the requirements described at
> https://docs.pytest.org/en/6.2.x/contributing.html#submitting-plugins-to-py…
>
> https://opentelemetry.io/docs/
> https://github.com/elastic/apm-pipeline-library/tree/master/resources/scrip…
>
> Thanks
> Ivan Fernandez Calvo
>
