Output may contain invalid import syntax when input file has leading ./

[gvanrossum]

I have a module containing the line

from __future__ import print_function

and I invoke pytype as

pytype ./yo.py -o -

Now the generated stub has invalid imports:

import ..__future__

print_function = ...  # type: ..__future__._Feature

[matthiaskramm]

Why is that stub invalid? You can totally do

import yo
yo.print_function

(I know the import __future__ in the pyi looks weird, but it's necessary to formulate the # type comment, and PEP 484 says that imports like this aren't re-exported)

[matthiaskramm]

(Also, if you're testing pytype right now, I should probably export a new version)

[gvanrossum]

Well, import ..__future__ is not valid Python syntax (note the two leading dots).

Also, yes I'm testing it, so would appreciate a new version.

[matthiaskramm]

Oh, I thought those two dots meant "some other imports not relevant to this bug".

Odd. I didn't even know pytype could generate relative imports.

[matthiaskramm]

Could you attach your yo.py?

Also, running an open-source export. It'll take a few hours (more if we hit a snag), we accumulated quite a few changes.

[gvanrossum]

Relative imports must use `from`, they can't use plain `import`. Thanks for doing the export!

[matthiaskramm]

Ah, I missed that you're using ./yo.py as path name. Good catch!

Export is done - pytype is now the newest version. (Will now verify that typeshed's travis still works)

[gvanrossum]

I overlooked the detail of the leading `./` for a long time too! Thanks for the export, will try it tomorrow.