-
Notifications
You must be signed in to change notification settings - Fork 546
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
Tox #327
Comments
Can you propose a |
I've added an example here The file tox.ini with comments:
Once this file is in place someone can just
When you run tox it creates a .tox/ directory where it installs new virtual Python environments which are used to run the tests. |
Yes, this is nice...we should definitely do this. |
Okay, I just tested this on napalm-ios. You accidentally dropped the [tox] header from the top of the tox.ini file.
Also will require that anyone that runs this has the relevant Python versions on their system (I had python34, but not python35 installed). Definitely helpful though as previously I was manually switching virtual environments which is a waste of time. |
Ah, sorry. Must have been a cut & paste bug.. Of course Yes if we test against three versions of Python changes are that most people will only have one 3.x version installed. I don't think that really matters though as this would just help people with testing against 2.7 and one of the 3.x versions. |
Yeah, agreed. I think it is definitely worth it. |
Looks super cool. We should have on the file whatever we want to test on travis and probably make sure travis uses it. Is it possible to also add coverage? |
Yeah Travis can call tox too. Regarding coverage that can be added too. I change the line in setup.cfg For pylama it was just silent since it didn't have anything to complain about. I've added a few extra lines to a file to make it complain below.
|
Regarding pylama, I deleted my own comment because I realized it was there and I had just missed it : ( |
FWIW the benefit of using something like Tox is to simplify the travis
configuration enough that it cuts down on what's needed for the user to run
the same tasks that travis would, on their laptop. That's the goal anyways
*Matt Oswalt*
Network Software Engineer
(c) 513.202.3138
(e) matt@keepingitclassless.net
(t) @Mierdin <http://twitter.com/mierdin>
(w) http://keepingitclassless.net/
…On Sat, Dec 10, 2016 at 3:36 AM, David Barroso ***@***.***> wrote:
Regarding pylama, I deleted my own comment because I realized it was there
and I had just missed it : (
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#327 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AECM-7yAGaBSNOsjVUR32JPKf6hpMuWIks5rGo7XgaJpZM4LFvkz>
.
|
I commented on the PR (napalm-automation/napalm-eos#107). I personally think we should move forward with this although I'd like to make sure it integrates nicely with travis. |
@napalm-automation/council would you mind taking a look to this? napalm-automation/napalm-eos#107 |
Closing this, as I think this will be solved anyway during the reunification. |
Description of Issue/Question
There was some discussion about using Tox in the PR I created for napalm-ios. Opening an issue for that since I removed tox.ini in the PR to get it merged.
I think it's quite nice to have tox since it allows people to test the code in a very easy way, especially for libraries which are to support both 2.7 and 3.
The text was updated successfully, but these errors were encountered: