[Discussion] It's a call for consideration to get rid of `tox.ini`

Proposal: Declare

Author: Sviatoslav Sydorenko <@webknjaz> IRC: @webknjaz

Date: 2019-04-10

• Status: New
• Proposal type: testing
• Estimated time to implement: 0.5 day

Motivation

Just because I can 😃

Problems

Having multiple processes-related config files is sometimes overwhelming.

Solution proposal

It’s possible to move the whole contents of tox.ini under the [tool.tox] section in pyproject.toml (recommended as a consolidation of tool configs via PEP 517/518). Ref: https://tox.readthedocs.io/en/latest/example/basic.html#pyproject-toml-tox-legacy-ini

Example

[build-system] requires = [ “setuptools >= 35.0.2”, “wheel >= 0.29.0”] build-backend = “setuptools.build_meta”

[tool.tox] legacy_tox_ini = “”" [tox] envlist = py27,py36

[testenv] deps = pytest >= 3.0.0, <4 commands = pytest “”"

Downsides include:

• need to already have pyproject.toml-aware version of tox on dev machines
• needs inlining which will break syntax highlighting and will probably make automatic config management painful…

Dependencies (optional)

N/A

Testing (optional)

N/A

Documentation (optional)

We’ll have to document the need for the latest tox.

Anything else?

N/A

[ssbarnea]

I am against this idea until we no longer need to use inline ini-in-ini approach. I would also want to see few other well known python projects adopting the new format. Molecule is already bleading-edge on its own.

Once we have at least 2-3 of our own dependencies already migrated to it, we can follow them.

[decentral1se]

Ah OK, missed it, woops. Any links / estimates on the native implementation (mentioned in https://tox.readthedocs.io/en/latest/example/basic.html#pyproject-toml-tox-legacy-ini)?