-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Add session.interactive to easily determine if Nox is being run by a human. #189
Comments
Why can't |
They can. But why make it harder than it needs to be? |
Also, we could add flags such as |
Well The |
True, but one requires (a) an import and (b) remembering what it is. I
actually filed this issue after forgetting what it was and having to look
it up for the 20th time.
…On Thu, May 16, 2019 at 8:58 PM Danny Hermes ***@***.***> wrote:
But why make it harder than it needs to be?
Well session.interactive and sys.stdout.isatty() are about the same
number of characters.
The --non-interactive flag is another story though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#189>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB5I47NVIPZ24WEMNJBSY3PVYUOHANCNFSM4HNIVRUA>
.
|
I took a stab at adding the interactive attribute. There is a pull request with the initial changes to add the interactive attribute. I have not added the --non-interactive flag yet. |
This was implemented in #196 |
How would this feature be useful?
In many cases its useful to know if nox is being run in an actual terminal or via CI or some other "headless" means.
Describe the solution you'd like
A new property on
Session
calledinteractive
. It would look like this:The text was updated successfully, but these errors were encountered: