Skip to content

Working directory unexpectedly set to wherever noxfile.py is. #469

@bcassell

Description

@bcassell

Describe the bug
Trying to invoke nox from a different folder using the --noxfile flag sets the current working directory to where the noxfile lives. This makes reusing a noxfile across multiple projects in a monorepo very difficult, since I can't find a good way to set the current working directory to where nox was called from. Even passing '.' as a posarg will end up being interpreted as the directory where the noxfile lives

Expected behavior
Either the cwd stays as wherever nox is called from, or we have some command line arg for what to treat as the cwd. If this feature already exists and I've missed it, or there are some other recommendations for how to use a single nox file across multiple projects, please let me know!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions