Any ideas?
I have tried resetting the system paths to the default, resetting the PythonEngine as well as restarting Rhino. All failed to solve it.
This happens only if I have something imported like from somepythonfile import *
Below that line I get no function hints.
Windows (PC) restart also doesnāt fix the issue.
In fact even if it is not * the function hint fails.
even if it is from something import something
Never had this issue before today.
This is the version I have: 6.15.19141.08361
Will install now: 6.16.19169.11231
Issue is still there
Looks like an example of a longstanding bug which appears to still be open:
If you search discourse for autocomplete or intellisense youāll see lots of problem reports over the years 
Thatās very weird.
Pity noone is even working on that issue and it was created 4 years ago. 
No problem here in the Rhino Python editor in Rhino 5
################################
### TEST CODE TEMPLATE ###
################################
import math
import rhinoscriptsyntax as rs
from Rhino import DocObjects
rs. # autocompletes normallyhmm I even get that when just:
import myscript
and also when the thing you import is none existent
(6.14)
but does it also happen after you run the script once? here it āfixesā the issue
I think it is not the from but importing a custom script that causes it
edit: just tested it in rhino 5 and same issue
so to work around: run the script once and you get your intelliSense back
by the way, donāt do this: from add_clipping_plane import * because explicit is better than implicit
This isnāt true.
I wrote the intellisense system that the current editor uses and there are many ways to break it. You found one. I believe I even called it intelliclunk in the UI.
Ahh yes I do get that if I import * from a module which contains nothingā¦
Iām sorry, I was referring to the:
Any way to fix that?
Iām pretty sure before today I have never experienced it.
I do this only when itās created by me and I have 2-3 methods inside. 
To save typing 2 or 3 methods ? 
to obfuscate what Iām doing there 
to be honest, before I started doing that I really didnāt find reason to split my projects in multiple files. But as it turns out the same method can be used in many projects and I naturally started splitting them all .
I always learn the hard way.
Not with the current system. Alain is investigating a completely new architecture for providing autocomplete in the future. Still just in the investigation stage though
Not this time: this time, in 6 months when you have forgotten which method came from where, you will be glad you listened to me 
Thatās not gonna happen since, like I said, I only have a couple of methods in each file 
and I hate using import * in cases when the file is not created by me.
here is one way that might fix it:
