You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
In be2cf3e, a hard dependency on Django was introduced by @jakirkham. I'd like to get rid of it again.
It is true that this package is not functional without Django, however, it is quite likely to be installed even in environments that don't make use of Django. This is because it is a dependency of Prospector, but could in general be pulled in by various Pylint setups.
Removing the dependency here would have the upside that such use would not needlessly pull in the heavy Django. It would also facilitate the use of this package together with a local development installation of Django. The downside is that the user has to depend on Django separately for this package to work, however, this is likely the case anyway, since the project that the user wants to check will rely on Django. Indeed, in this sense the dependency here might mask a missing dependency in the downstream project's setup.
@jakirkham, @conda-forge/pylint-django, what do you think?
Installed packages
-
Environment info
-
The text was updated successfully, but these errors were encountered:
Solution to issue cannot be found in the documentation.
Issue
In be2cf3e, a hard dependency on Django was introduced by @jakirkham. I'd like to get rid of it again.
It is true that this package is not functional without Django, however, it is quite likely to be installed even in environments that don't make use of Django. This is because it is a dependency of Prospector, but could in general be pulled in by various Pylint setups.
Removing the dependency here would have the upside that such use would not needlessly pull in the heavy Django. It would also facilitate the use of this package together with a local development installation of Django. The downside is that the user has to depend on Django separately for this package to work, however, this is likely the case anyway, since the project that the user wants to check will rely on Django. Indeed, in this sense the dependency here might mask a missing dependency in the downstream project's setup.
@jakirkham, @conda-forge/pylint-django, what do you think?
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: