Skip to content

Autodetection no longer works #292

@carlio

Description

@carlio

One of the original points of prospector was to automatically tweak linting rules to avoid issues specific to certain frameworks, for example in Django some values do not exist until run time and are picked up by

This also breaks the uses configuration in profiles or from the command line.

Restoring pylint-django / pylint-celery / pylint-flask fixes this problem. Various profiles with uses: django will be broken currently.

The original complaint was due to installing Django when it was required but that has been removed from pylint-django and this was never a similar problem for pylint-celery or pylint-flask

I finally found out where this was removed and it seems to be part of a completely unrelated PR and was quickly added in as a result of a comment on a separate issue so to separate them out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    [ready for release]Label for issues which have been fixed in the develop branch but have not been released to PyPI yet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions