Hello Kedro people! I wonder if anyone has been able to resolve this annoying issue of VSCode's

pylance

incorrectly inferring that the

pipeline

function (as imported from

kedro.pipeline

is actually a module. It gets in the way of showing the proper documentation for

kedro.pipeline.modular_pipeline.pipeline()

, and I figure could turn some less Kedro-savvy devs away by thinking they're doing it wrong (me a while back 🙃)

https://github.com/kedro-org/kedro/issues/2805 Hey @Higor Carmanini Did you join the training today? Thanks for raising that, I didn’t know this is an issue as I don’t notice this problem before ( I started using kedro 3 years ago).

I did not, that's probably just a coincidence 😄 But great to see someone else already pointed that out. That has confused me for a while, only last week I found out that

pipeline

was not a module being called.

I believe this is a relatively new issue(or regression), I wonder if Pycharm has the same problem?

I just realized there is also a

pipeline.py

module inside

kedro.pipeline

, so the clash is not that much of a surprise now. Could be the static checker's lookup priority/order, if that makes sense. There's a reference ambiguity when it comes to

kedro.pipeline.pipeline

.

I am more convince this is a Pylance issue, can you try upgrade the Pylance version? I test it with another computer today and I don't see any error.

It is already the latest version (other than the pre-release) v2023.7.20. And this has been happening consistently for me in VSCode. Can you show me a screenshot of how it shows to you?

image.png

Dang, I always miss notifications from this Slack. No, I don't think I'm using any specific configs to

pylance

:

"python.analysis.typeCheckingMode": "basic",
    "python.analysis.autoFormatStrings": true,
    "python.analysis.enablePytestSupport": true,
    // "python.analysis.inlayHints.callArgumentNames": true,
    "python.analysis.inlayHints.functionReturnTypes": true,
    "python.analysis.inlayHints.pytestParameters": true,
    "python.analysis.inlayHints.variableTypes": false,
    "python.analysis.useLibraryCodeForTypes": true,

I can reproduce the same behavior in my own laptop. Not sure what’s the best way to fix it without breaking imports