Skip to content

tox needed? #2310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
guettli opened this issue Mar 14, 2017 · 2 comments
Closed

tox needed? #2310

guettli opened this issue Mar 14, 2017 · 2 comments
Labels
type: question general question, might be closed after 2 weeks of inactivity

Comments

@guettli
Copy link

guettli commented Mar 14, 2017

I found this while reading the docs:

... you can use tox to make sure that the package is really correct and tests pass in all required configurations.

Source http://docs.pytest.org/en/latest/goodpractices.html#goodpractices

I am unsure.

Most open source software gets hosted in github today.

On github you have travis.

Travis can do this (test different configurations and Python versions).

For the common use case I see no use for tox.

Since the audience of above text are new comers, I would provide the simple solution first.

Before advising to use tox, I would state that you can use travis at github.

What do you think?

@RonnyPfannschmidt
Copy link
Member

tox is locally usable, travis isnt and needs different setup, its not even closely the same

@RonnyPfannschmidt RonnyPfannschmidt added the type: question general question, might be closed after 2 weeks of inactivity label Mar 14, 2017
@nicoddemus
Copy link
Member

Not only that, tox is considered the defacto standard for running tests in python projects, so much that most projects have a tox file and use tox on Travis for CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question general question, might be closed after 2 weeks of inactivity
Projects
None yet
Development

No branches or pull requests

3 participants