Hi everyone 👋,

Full disclosre, I'm not a user of doctests in general (although I've contributed to pytest's doctest support in the past).

I see the following pytest-doctestplus features that are not available in pytest's core:

Float comparison
Ignoring warnings
Skip unconditionally
Dependencies
Remote Data (depends on pytest-remotedata)

All of them (except perhaps for "Remote Data" support) seem reasonable to have in the core.

As @bsipocz mentions, usually we prefer to extend pytest through plugins, but for features of the standard library where there's really not much diverting ways to go about it, integrating that feature into the core makes sense. To me doctesting falls into that category.

For an example of a feature that's in the standard library but we don't have plans to integrate into the core is async support: asyncio is in the standard library, but there are other libraries with asynchronous support , like trio and twisted, so it makes sense to have separate plugins for each: pytest-asyncio, pytest-trio, and pytest-twisted.

Integrating this to the core would require a champion however, someone who's willing to do the integration work and step up on occasion to help fix bugs on that module if they appear (of course core devs often help here, but is nice to have a champion/expert to turn to).

One advantage is that there would be no more compatibility problems, as they are now in the core so compatibility is guaranteed.

Having said all that, if a champion steps up, I would definitely be 👍 to integrate pytest-doctestplus into the core. I'm sure it would be very much appreciated by doctest users, as it introduces some very nice features.

@RonnyPfannschmidt @bluetech, opinions?

Why is this not part of pytest? #100

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions