sobolevn

@mahmoud hm, I have not considered lists and objects. So, there are multiple cases how to handle them. ## Lists ### Exceptions ```python glom([1, 2, 3], Move('1', Spec('0'))) # =>...

Thanks @mahmoud! I am pretty sure that leaving something in a broken state is not a good idea. So, this operations must be transactional. I guess, this will bring an...

Friendly ping.

@DmytroLitvinov can you please make a PR with the fix to `wemake-django-template`?

Ok, @bradmontgomery, here's my plan: 1. Separate [`count_queries`](https://github.com/bradmontgomery/django-querycount/blob/master/querycount/middleware.py#L64) into its own `queries.QueriesCounter` class 2. Separate [`print_num_queries`](https://github.com/bradmontgomery/django-querycount/blob/master/querycount/middleware.py#L169) and [`stats_table`](https://github.com/bradmontgomery/django-querycount/blob/master/querycount/middleware.py#L117) into `reporter.ConsoleReporter` class 3. Update docs 4. Write tests How I see...

Well, that's just an example 🙂

@jllorencetti oh, that's a surprise for me. Could you please explain this design decision? Current behavior makes the process a lot less pleasant.

So, can I make this change? I see it to be like this: 1. When running with `--dead-fixtures` tests are collected and executed as usual 2. If some dead fixtures...

I am not aware of any existing solutions in this field. We can add extra flag `--requirements-production-mode` which will indicate that we are running in the production environment.

+1 this is totally required. @matllubos thanks!