Hi was anyone able to get the code completion working in PyCharm? There seem to be something with _utilities.lazy_import so that PyCharm does not provide any completion at all. Then in VScode, you get completion working but it's not great either when I use Show Bover on the resource it does not show almost anything. For this example:

"""A Python Pulumi program"""

import pulumi

from pulumi_aws import iam

iam.Role()

Show Hover action only shows

(class) Role

- while I expect the whole docstring to show up. But it looks like the cause of this is that how docstrings are written and possibly usage of overload decorator as well

class MyClass:
    @overload
    def __init__(self, a:int)->None:
        """init INT"""
        ...
    def __init__(self, *args, **kwargs) -> None:
        pass # real implementation

If Classes had a class docstring like this it would at least shown that:

class MyClass:
    """A class doc."""
    @overload
    def __init__(self, a:int)->None:
        """init INT"""
        ...
    def __init__(self, *args, **kwargs) -> None:
        pass # real implementation

I wonder if pulumi adheres to any of the styling guides or "just generates docstrings"

Hey! So, the TL;DR is you’re right about some of this, and some of it is a little obscured. I captured the issues in detail over at https://github.com/pulumi/pulumi/issues/7367, you might be able to get some information there to get it to work for you but we do have some work to do.

Yeah and I prefer Numpy style 😄 However, Goolge style classes suggest naming attributes in class docstring which can actually fix the problem at least partially 🙂 https://google.github.io/styleguide/pyguide.html#384-classes

@great-sunset-355 appreciate you looking into this. Please leave these comments in the issue so we can have a record when we go to fix, we’d like to keep github issues as the place to discuss bugs and possible fixes as we don’t all monitor this slack and it may not be me working on the issue 🙂

yes I just wanted to make sure we want to track this in a single issue not a separate one