You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the documentation chapter "Using a configuration file" please disregard the example placing a [tool.phmdoctest] section in setup.cfg. Pytest 7 advises a [tool:*] (colon) and discourages use in setup.cfg. I suspect some other tools may use the colon to discover tool configuration sections in setup.cfg.
For the next version of phmdoctest >1.4.0:
Add advice to prefer the .toml format followed
by .ini. and finally .cfg.
Allow[tool:phmdoctest] in *.cfg.
Allow [tool.phmdoctest] in *.cfg to remain back
compatible with phmdoctest 1.4.0.
Note that the name of the configuration file is explictly passed to phmdoctest in place of the Markdown file. There is no requirement to place the configuration section in an existing configuration file. It can be placed in a new file.
The text was updated successfully, but these errors were encountered:
In the documentation chapter "Using a configuration file" please disregard the example placing a
[tool.phmdoctest]
section in setup.cfg. Pytest 7 advises a [tool:*] (colon) and discourages use in setup.cfg. I suspect some other tools may use the colon to discover tool configuration sections in setup.cfg.For the next version of phmdoctest >1.4.0:
.toml
format followedby
.ini.
and finally.cfg
.[tool:phmdoctest]
in *.cfg.[tool.phmdoctest]
in *.cfg to remain backcompatible with phmdoctest 1.4.0.
Note that the name of the configuration file is explictly passed to phmdoctest in place of the Markdown file. There is no requirement to place the configuration section in an existing configuration file. It can be placed in a new file.
The text was updated successfully, but these errors were encountered: