- Mar 20, 2018
-
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
render_to_response is deprecated in Django 2.0 and render has been available since 1.3. It's shorter to write and avoids the writing of context_instance=RequestContext(request) in each of its call.
-
Samuel GAIST authored
Fix backup restore See merge request !236
-
Samuel GAIST authored
This ensure that whatever the outcome of the tests, the prefix is cleaned up. Currently these are piling up in the /var/tmp folder.
-
Samuel GAIST authored
-
Samuel GAIST authored
-
Samuel GAIST authored
-
Samuel GAIST authored
-
Samuel GAIST authored
-
Samuel GAIST authored
-
Samuel GAIST authored
The natural key generate was using a tuple in a tuple (which is good) however the get_by_natural_key method was expecting a flat tuple.
-
Samuel GAIST authored
This allows Django to serialize the database content in the correct order.
-
Samuel GAIST authored
-
Samuel GAIST authored
Database hash doesn't exists anymore and rather than generating natural keys that trigger the creation of get_by_natural_key methods with way too many parameters, use tuples in tuples. This make the code clearer to read as well as easier to maintain if the natural key of a related field changes.
-
Samuel GAIST authored
-
Samuel GAIST authored
Now Docker is used with all the parameters it allows to set when running a container.
-
Samuel GAIST authored
-
Samuel GAIST authored
beat.core must be 1.6.x beat.backend.python must be 1.5.x
-
-
-
Samuel GAIST authored
Performance fixes Closes #488 See merge request !234
-
Includes: - ng-model debouncing - track bys for ng-repeat - rmd isUniqueTableable - memoized funcs Fixs #488
-
Samuel GAIST authored
Checkout the beat.backend.python_v1.4.2_1 tag for beat.examples See merge request !237
-
- Mar 16, 2018
-
-
Samuel GAIST authored
This fixes the issue that the examples on the latest master are using the 1.5 version of the python backend which is not yet released. Relates to: beat.examples#12
-
Samuel GAIST authored
Cache bugfix See merge request !233
-
Samuel GAIST authored
Fix angular dependency injection scheme See merge request !232
-
- Jan 10, 2018
-
-
Jaden DIEFENBAUGH authored
-