Julien Enselme

@Somethingideally still broken :-(

I am also interested in that functionality. Any plans on integrating it?

I think I encountered this issue today. Marking the tests with `@pytest.mark.django_db(transaction=True)` instead of `@pytest.mark.django_db()` solved it for me.

Indeed, I noticed that also. I might be reverting to using the sync HTTP client and wrap async operations in `async_to_sync` where needed to prevent this. I had a look...

As far as I know this post of July 2016 is the last info we got. I think it would be nice to have an update.

In addition to my PR #74, if you can't apply it, you should be able to prevent the issue by passing a custom environment: ```python from secretary import Renderer, UndefinedSilently,...

What I think would be awesome is to have an option to make exit csvclean with a non 0 status code if errors are detected. That would make it easy...

Hello, I have the same configuration. Any progress on this issue? Thanks

Not exactly. What is covered by README.md is a multisite with sub1.example.com, sub2.example.com, …, ie multisite with a subdomain per site. There are also many examples for that configuration on...

I found out how to adapt the script to handle this situation : - before `location /`, add ``` location /SUBSITE { try_file $uri @SUBSITE; } ``` - Then add:...