-
-
Notifications
You must be signed in to change notification settings - Fork 105
[TODO] Figure out how to integrate tox --devenv
into Makefile
#364
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
Comments
I can take a look at this. |
We can now create the dev environment using tox. All you have to do is run `make dev` and tox will create a virtualenv for you. Fixes aio-libs#364
Sure, go ahead! |
We can now create the dev environment using tox. All you have to do is run `make dev` and tox will create a virtualenv for you. Fixes #364
#370 doesn't do what the issue asks. This is still unsolved. |
sorry i misunderstood what do you need it to do ? |
The issue title says that you need to integrate |
so something like
|
I'm currently not 100% sure how this should look for the dev flow: maybe we just need a number of separate targets, or maybe we could just rely on the current Python too. The biggest challenge is to figure out what is the best UX for us. |
@hmajid2301 it could also be helpful if you could record the use of the make target with https://asciinema.org. |
PR #371 by @hmajid2301 * Create the dev environment using tox We can now create the dev environment using tox. All you have to do is run `make dev` and tox will create a virtualenv for you. Fixes #364 * Make changes Made changes suggested by webknjaz, also recorded a session with aciinema, https://asciinema.org/a/GAenipsSb0hZfG8Q8pn2ZWRiR. * Rename `dev` target into `dev-env` Co-authored-by: Sviatoslav Sydorenko <[email protected]>
tox-dev/tox#1326
The text was updated successfully, but these errors were encountered: