Skip to content

Conversation

@jnmclarty
Copy link
Contributor

Minor clarification and addition of links to the docs, just to close #683.
#683 could have probably been closed before this PR, but if somebody had a different idea of where this should go in the docs, I could modify this PR.

As rendered:
http://imgur.com/a/FSTpP

@gvanrossum
Copy link
Member

I recommend removing the mention of Ellipsis; pass and ... are the only reasonable options.

@jnmclarty
Copy link
Contributor Author

@gvanrossum your feedback slightly contradicts the open issue #683. So, I removed the comment about it being an option, but left the link to Ellipsis itself.

@jnmclarty
Copy link
Contributor Author

I was expecting somebody to point to a section of the docs where it would make sense to add the explanation for the other use case. That is...

x = ... # type: int

I can make an attempt in docs/type_inference_and_annotations.txt

@gvanrossum
Copy link
Member

gvanrossum commented Jun 3, 2016 via email

@jnmclarty
Copy link
Contributor Author

That makes more sense to me, now. I've adjusted accordingly. I can squash whenever necessary.

class B(A):
def foo(self, x: int) -> None: ...
def bar(self -> str:
def bar(self) -> str:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this fix!

@jnmclarty
Copy link
Contributor Author

stubfiles

@jnmclarty
Copy link
Contributor Author

stubfiles2

@gnprice gnprice merged commit 7a2e42a into python:master Jun 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document uses of ellipsis in stubs

3 participants