Opened 2 years ago

Closed 2 years ago

#26916 closed enhancement (fixed)

Make tox config more useful/friendly for running multiple interpreters/versions

Reported by: dmr Owned by: dmr
Priority: Medium Milestone:
Component: Archived/Stem Version:
Severity: Normal Keywords: dev testing
Cc: Actual Points:
Parent ID: Points:
Reviewer: atagar Sponsor:


Right now tox can be a bit of a pain for dev usage.
This ticket is intended to remove some of the hassle for multiple interpreters/versions, and make the default environments config a bit more useful.

I've identified a few improvements under this theme - these are better described in commits.

atagar: I've got a PR coming soon

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by dmr

Reviewer: atagar
Status: assignedneeds_review

Pull request:
branch head e82b3f4317e544e9fce61fc8d93b4cbb72263fd3

Handy 'lil --no-ff merge commit there to sum things up, too.

For reference, these changes were done for tox --version 2.5.0, on Debian stretch.

There may be some tox version dependencies to look out for here. I'd really appreciate a sanity check on another system :).

I'd especially like you to check whether the pypy environment works for you (see a3414913275192163ae186d86c7bcaff5e7be5e9). I saw that stem is now aiming for pypy compatibility, and I'm really hoping this PR helps simplify testing across versions in the future!

For instance, I think this will be one of the most common commands I run while developing:

tox -- -u -q

time for that clocks in around 20s for me on py27,py35

comment:2 Changed 2 years ago by atagar

Resolution: fixed
Status: needs_reviewclosed

Thanks Dave, pushed.

Note: See TracTickets for help on using tickets.