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.

Sign up for GitHub

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

Jump to bottom

_meta is official API #66

Closed
koterpillar opened this issue Mar 4, 2016 · 4 comments
Closed

_meta is official API #66

koterpillar opened this issue Mar 4, 2016 · 4 comments

Comments

@koterpillar
Copy link

With _meta being brought into the public API, it makes sense to exclude it from protected-access.
carlio added a commit that referenced this issue May 22, 2016
@carlio
[refs #66] Testing to see if access to _meta on models is allowed
93fd041
@carlio
Copy link
Collaborator

carlio commented May 22, 2016

@koterpillar do you have an example where this is triggered? I just created a test-case for this and it seems like protected-access is not raised. I tried with django 1.9 and 1.7 and both seemed ok. What version of pylint are you running?

@koterpillar
Copy link
Author

Please try MODEL._meta.get_field('ursuary') in your example.

@carlio
Copy link
Collaborator

carlio commented May 22, 2016

@koterpillar Ah brilliant thanks, test is now failing, so I'll look into suppressing that warning 👍

@carlio
Copy link
Collaborator

carlio commented May 25, 2016

Fixed in develop branch with e044f83 , will add to a release soon

@carlio carlio closed this as completed May 25, 2016
This was referenced Jul 16, 2017
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@koterpillar @carlio