-
-
Notifications
You must be signed in to change notification settings - Fork 767
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
test_environment_not_sourced fails on my Ubuntu #1032
Comments
yeah this test was tricky to write and properly the first failure is due to having The second failure is due to not having |
regarding the second failure.
I found out that you delete the [testenv:venv] section in your azure-pipelines commit. any reason to do it? |
ah right, I deleted that because I don't use it myself and it defaulted to python 2 which is not great That can probably be updated to |
but the advantage of using this venv was that it didn't run any tests and it was created in the root directory and not inside the .tox directory.
BTW, If you are not using it, what do you use? |
oh, I meant |
I don't like this proposal. |
myself I mostly use virtualenv venv
. venv/bin/activate
pip install -r requirements-dev.txt I wonder if @gaborbernat would be ok with me adding some feature to tox that's like It's probably fine to put back the |
sure. Thanks. I'll do it tomorrow. |
@asottile I'm fine with that but I think a lot of things are derived from envdir 🤔 |
I'll see what I come up with 👍 |
regarding the first error. Here is some logs that might help:
and the path from the test:
|
ah yeah this path will have a ideally |
and why do |
the
This test is demonstrating what happens when all three of those are blown away / unavailable |
During my working on pre-commit I notice that one of the tests fails in tox.
Here is an example
Here is when I'm using pytest for only this test:
The text was updated successfully, but these errors were encountered: