Prevent "Cannot find a reference" warnings about pyats

[simingy]

most likely because

ats.topology.loader module is replaced as an instance of the Loader class in sys.modules. That tends to cause pylint to panic.

[extsoft]

Looks like. Anyway, the stub files have to solve this problem without changing a code.
@siming85 what do you think about? Are there other options?

[simingy]

isn't stub files only part of Python3.5?
we could change the implementation slightly so it doesn't yell at you like that - it'll be an easier fix.

atm we still support python 3.4, so stubs won't fix that.

[extsoft]

isn't stub files only part of Python3.5?

@siming85 the subfiles aren't dependent on a Python's versions. They even can be separated from the initial code (here is the documentation). To work with them, you need to have typing module. It's built-in in Python 3.5 or greater. For other, you can install it with pip install typing.
Anyway, you have a better understanding of how to fix it.

From the other side, do I have to create a separate issue for each similar case? For instance, if I write with: from ats.aetest import CommonSetup, then the warning will appear.

[simingy]

this should be fixed in the next release.

[simingy]

fixed in pyATS release v5.0.0, available as of Oct 9