Skip to content

Conversation

@ryan-copperleaf
Copy link

Replacement for #50; fixes #49.

@coveralls
Copy link

coveralls commented Dec 21, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 19ba836 on copperleaftech:django-2.0 into 1a6ea28 on miki725:master.

such as ``ForeignKey``.
"""
try:
name = field.remote_field.name
Copy link
Owner

Choose a reason for hiding this comment

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

usually this results is lower coverage when running against a particular version of a dep. maybe do something like this?

name = (getattr(field, 'remote_field', None) or field.rel).name

the or to make the evaluation lazy in case first one succeeds

I know this is not exactly pythonic but I guess Im a sucker for the coveted 100% coverage locally...

Copy link
Author

Choose a reason for hiding this comment

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

Sure.

@coveralls
Copy link

coveralls commented Dec 21, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling adfc279 on copperleaftech:django-2.0 into 1a6ea28 on miki725:master.

@vmihalachi
Copy link

Hi, any news on that?
Can't upgrade to Django 2 because of that :/

@rajesh-h
Copy link

Hi Team,

Will this be implemented soon?

Thanks

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.

Does not work with Django 2.0

6 participants