Flávio Juvenal

Thanks for reporting back @Jdsleppy Since version 1.0.0, both projects must always match versions in order to work correctly. Therefore, if one uses `django-webpack-loader==1.6.0`, they must use `[email protected]`. Even if...

Related: https://github.com/django-webpack/django-webpack-loader/pull/172

Another alternative seems to be contextvars (Python built-in). The library django-guid uses that: https://github.com/snok/django-guid/blob/main/django_guid/middleware.py And it seems they're a safe replacement for threading.local that works with asyncio as well: https://peps.python.org/pep-0567/#examples

Thanks. Superseded by https://github.com/django-webpack/webpack-bundle-tracker/pull/111

@JensHeinrich is right. Due to https://github.com/PyCQA/bandit/blob/ca4faf2f82a7c68a088100f8ba2b8e56f9bdcfe3/bandit/core/manager.py#L245-L253 bandit will scan a file included in a commit regardless of whether it's excluded. I had to add my exclusions from .bandit file in...

I'll leave this open just in case we Dockerize production builds.

Closed per last comment.

In general, pylint is too strict to use in settings files. Closing.

For posterity: possibly not django-webpack-loader specific. Closing for now.

Thanks for the report @browniebroke. Yes, please feel free to open a PR!