thenewguy

my settings file got mangled by GitHub Flavored Markdown

@bharling did this work out for you?

I think we should actually use "π" as the default javascript namespace. This could be configurable in case pyjaco is building for an environment that does not support unicode identifiers?

So I read more into this. My current case is using EFS. I assumed that the lifecycle rules would be the same between EFS and S3. I've done some reading...

Google Storage lifecycle policies do not seem to place a restriction on minimum file size per https://cloud.google.com/storage/docs/lifecycle and it also indicates that specific expiration policies are available. And neither does...

The basic difference is the access speed. The filesystem storage recomputes the hash (https://github.com/antonagestam/collectfast/blob/master/collectfast/strategies/filesystem.py#L9) for remote files. It would be better to add an additional file that contains the hash...

It would be sweet if nested inlines were supported. https://github.com/silverfix/django-nested-inlines

https://github.com/chrisglass/django_polymorphic

I pinned to `django-redis-cache==2.1.0` in my constraints and the issue went away

I just had this error with 2.1.3 as well. Not sure what happened but I guess the release is messed up