Output may contain invalid import syntax when input file has leading ./ about pytype HOT 8 CLOSED

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)

from pytype.

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

from pytype.

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.

from pytype.

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.

from pytype.

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.

from pytype.

from pytype.

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)

from pytype.

from pytype.