Skip to content

Demonstrate a problem with attrs w/ annotations #750

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

Closed

Conversation

webknjaz
Copy link

@webknjaz webknjaz commented Feb 7, 2020

Steps

  • For new features or bug fixes, add a ChangeLog entry describing what your PR does.
  • Write a good description on what the PR does.

Description

This PR extends attrs tests in order to demonstrate a not-yet-covered case described in #724.

Type of Changes

Type
🐛 Bug demo

Related Issue

N/A

@PCManticore
Copy link
Contributor

Hey @webknjaz Thanks for the PR. I'm not entirely sure what's the problem exactly? Can you open an issue instead?

@webknjaz
Copy link
Author

Yes sure. Looks like it's the issue already exists: #724.

@webknjaz
Copy link
Author

@belm0 is this what you asked in #724?

@belm0
Copy link
Contributor

belm0 commented Feb 11, 2020

I mentioned later in the original issue, but this is foremost a deficiency of type-annotated attributes on plain classes (not using attrs library).

#724 (comment)

I gave example code there ("obj.o2.foo2()" should yield a pylint warning).

@webknjaz
Copy link
Author

Oh, so almost the same but not quite.

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.

3 participants