jedi automatic completion missing about jedi HOT 9 CLOSED

The ".pyi" file is stored in the same level directory as the so file.

from jedi.

Can you show me the pyi file?

from jedi.

And next time please don't post screenshots of texts. It is way better to have this in a way so I can copy it.

from jedi.

Can you show me the pyi file?
Tks you for your reply.

class Device:
    def __init__(self) -> None: ...
    def set_io(self, input: str, parameters: dict, current_output: str, dataset_out: str, output: str, log_out: str) -> None: ...

My wheel package is on the bastion machine，so I can't upload the wheel package to github directly. I confirm that the 'pyi file' can be recognized by pycharm.
the structure of wheel package are as follows:
esimkit
|--edevice.cpython-39-x86_64-linux-gnu.so
|--edevice.pyi
| ...

from jedi.

If I have no way to reproduce your problem you have to either help me or we can close the issue as well. It's pretty much impossible for me to debug this now.

from jedi.

If I have no way to reproduce your problem you have to either help me or we can close the issue as well. It's pretty much impossible for me to debug this now.

the wheel package and the source code 'test.py' are in the package, you can debug it. Tks a lot

esimkit.zip

from jedi.

Can you provide me with a minimally reproducible example? It doesn't feel like I'm ever going to look into this otherwise.

from jedi.

Can you provide me with a minimally reproducible example? It doesn't feel like I'm ever going to look into this otherwise.

Actually, you only need to do two steps:
Install the wheel package in 'build/dist', and then debug 'test.py'.

There may be version compatibility issues when installing the wheel package, so in case of incompatibility, you need to compile the wheel package yourself and install it. All operation steps are in README.md

from jedi.

I don't think you understand, because you might be new to this:

It is not my job to do your work. You have to convince me that this is really a bug. And to do that you typically have to invest an hour or so to write up a good issue that is as small as possible. This is what I do and this is what all experienced devs to when they report issues. What you do is to throw a bunch of code at me and say "it doesn't work". That is not very helpful.

I'm going to close this issue for now until you provide me with a better reproduction. I'm happy to reopen if there's a minimal reproducible example.

from jedi.