Is '--no-deps --no-build-isolation' needed for Python given conda-build defaults?

[matthewfeickert]

In PR #480 the use of --no-deps --no-build-isolation was introduced as defaults for Python pip installs

grayskull/grayskull/strategy/pypi.py

Line 66 in 9d5d5e2

] = "<{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation"

(now at

grayskull/grayskull/strategy/pypi.py

Line 67 in 5b29307

"<{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation"

)

However, as @henryiii points out in conda-forge/packaging-feedstock#32 (comment), conda-build already sets these defaults

...
    env["PIP_NO_BUILD_ISOLATION"] = "False"
    # some other env vars to have pip ignore dependencies.
    # we supply them ourselves instead.
    env["PIP_NO_DEPENDENCIES"] = True
    env["PIP_IGNORE_INSTALLED"] = True
...

Is there any reason to have these (good options for conda package builds) duplicated here so that they appear explicitly in conda package repiece meta.yaml files?

[matthewfeickert]

Got beaten out by Henry as he opened Issue #582 just ahead of me, so closing as duplicate of that.