Pytest.ini sudo option.

[MicroNateId]

Please add the option of sudo in pytest.ini.

Some scripts require sudo elevation to run in VSCODE and there's no clear way to do this.

[eleanorjboyd]

Hello- could you clarify what you mean here? You want to be able to run pytest with sudo level permissions? And you want this to be possible through the pytest.ini file? That file and its rules are set by pytest, all we do is run pytest and it picks the ini file up.

[MicroNateId]

Yes, I have several Tests that interact with an AMD python api that requires system root access. Not sure if there is a way to implement this similar to what is done with the debugger sudo option?

…

On Mon, Nov 11, 2024, 9:51 AM Eleanor Boyd ***@***.***> wrote: Hello- could you clarify what you mean here? You want to be able to run pytest with sudo level permissions? And you want this to be possible through the pytest.ini file? That file and its rules are set by pytest, all we do is run pytest and it picks the ini file up. — Reply to this email directly, view it on GitHub <#24411 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSG5TCXH5RANVQ36ZHQ7M32ADOBZAVCNFSM6AAAAABROPA5XCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGYZDINBUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MicroNateId]

Adding some more context. I've found a workaround that is temporary at best (changing the path of the pytest to "sudo pytest" within the configs) however, this causes issues as the vscode Test interface creates a lot of files when running and having them be owned by root is randomly causing issues.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[eleanorjboyd]

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue. PRs are welcome so you can create a PR that fixes this if you are passionate about getting this feature across the finish line. Thanks!