Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call tips not handling string annotations properly #511

Closed
GoogleCodeExporter opened this issue Aug 24, 2015 · 2 comments
Closed

Call tips not handling string annotations properly #511

GoogleCodeExporter opened this issue Aug 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.
2. def g(distance:"in meters"):  pass
3. g(

What is the expected output? What do you see instead?

In the editor's call tip, I expect to see the annotation on distance, ie 
distance:"in meters".  It works fine if the annotation is a typename like Int, 
but when the annotation is a string, as above, it incorrectly pops up the tip 
as  
     distance:"`````````"

What version of the product are you using? On what operating system?
PyScripter 2.4.1.0, Python 3.1.3, Windows 7.

Please provide any additional information below.


Original issue reported on code.google.com by p.wentwo...@ict.ru.ac.za on 25 May 2011 at 8:03

@GoogleCodeExporter
Copy link
Author

Fixed in version control.

Original comment by pyscripter on 15 Jun 2011 at 12:36

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Now annotations also work in the interpreter window.

Original comment by pyscripter on 15 Jun 2011 at 12:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant