🔐 Sid Gifari File Manager Pro
v8.0.5 | 2026-08-10 03:03:12 | PHP 8.2.33
📂
/ (Root)
/
opt
/
cloudlinux
/
venv
/
lib
/
python3.11
/
site-packages
/
pylint_django
/
tests
/
input
📍 /opt/cloudlinux/venv/lib/python3.11/site-packages/pylint_django/tests/input
🔄 Refresh
✏️
Editing: external_tastypie_noerror_foreign_key.py
Read Only
""" Checks that Pylint doesn't raise an error when a 'ForeignKey' appears in a non-django class The real case is described as follow: The project use tastypie and django. tastypie has a `ForeignKey` field which has the same name as django's `ForeignKey`. The issue is the lint trys resolving the `ForeignKey` for the tastypie `ForeignKey` which cause import error. """ from tastypie import fields from tastypie.fields import ForeignKey # pylint: disable=missing-docstring from tastypie.resources import ModelResource class MyTestResource(ModelResource): # pylint: disable=too-few-public-methods field1 = ForeignKey("myapp.api.resource", "xxx") field2 = fields.ForeignKey("myapp.api.resource", "xxx")
💾 Save Changes
❌ Cancel