You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the import module as name construct is used then it is name that is added to imports rather than module. I am definite that this must be fixed. Besides, in case of the from module import names statement names are added to imports as is. For example from sys import * will result in the * entry in the imports section. I propose to fix it by prepending the module name to the imported name. For example the following statement
from sklearn.model_selection import train_test_split
must be registered in the imports section as sklearn.model_selection.train_test_split (whereas now it is registered as train_test_split).
The text was updated successfully, but these errors were encountered:
If the
import module as name
construct is used then it isname
that is added to imports rather thanmodule
. I am definite that this must be fixed. Besides, in case of thefrom module import names
statementnames
are added to imports as is. For examplefrom sys import *
will result in the*
entry in the imports section. I propose to fix it by prepending the module name to the imported name. For example the following statementmust be registered in the imports section as
sklearn.model_selection.train_test_split
(whereas now it is registered astrain_test_split
).The text was updated successfully, but these errors were encountered: