dedsm

import logging

from django.contrib.gis.db.backends.postgis.base import \
    DatabaseWrapper as PostgisDBWrapper
from django.db import ProgrammingError

from .schema import TimescaleSchemaEditor

logger = logging.getLogger(__name__)

darklow

from celery import Task
from celery.task import task
from my_app.models import FailedTask
from django.db import models

@task(base=LogErrorsTask)
def some task():
    return result
    
class LogErrorsTask(Task):

hakib

"""
Custom django checks.

    H001: Field has no verbose name.
    H002: Verbose name should use gettext.
    H003: Words in verbose name must be all upper case or all lower case.
    H004: Help text should use gettext.
    H005: Model must define class Meta.
    H006: Model has no verbose name.
    H007: Model has no verbose name plural.

adamchainz

# refactor of https://lukeplant.me.uk/blog/posts/double-checked-locking-with-django-orm/
# untested

def double_checked_lock_iterator(queryset):
    for item_pk in queryset.values_list("pk", flat=True):
        with transaction.atomic():
            try:
                yield queryset.select_for_update(skip_locked=True).get(id=item_pk)
            except queryset.model.DoesNotExist:
                pass

djspiewak

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

• Two developers working on independent features must never be blocked by each other
  • No code freeze! Ever! For any reason!
• A developer must be able to base derivative work on another developer's work, without waiting for any third party
• Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
• Developers must be able to work on multiple features simultaneously, or at lea

danni

from django import forms
from django.contrib.postgres.fields import ArrayField


class ChoiceArrayField(ArrayField):
    """
    A field that allows us to store an array of choices.
    
    Uses Django 1.9's postgres ArrayField
    and a MultipleChoiceField for its formfield.

spookylukey

class AfterFetchQuerySetMixin:
    """
    QuerySet mixin to enable functions to run immediately
    after records have been fetched from the DB.
    """
    # This is most useful for registering 'prefetch_related' like operations
    # or complex aggregations that need to be run after fetching, but while
    # still allowing chaining of other QuerySet methods.
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)

althonos

# https://gist.github.com/althonos/6914b896789d3f2078d1e6237642c35c

[metadata]
name = {name}
version = file: {name}/_version.txt
author = Martin Larralde
author_email = martin.larralde@embl.de
url = https://github.com/althonos/{name}
description = {description}
long_description = file: README.md

ostcar

class IdManyRelatedField(ManyRelatedField):
    field_name_suffix = '_ids'

    def bind(self, field_name, parent):
        self.source = field_name[:-len(self.field_name_suffix)]
        super().bind(field_name, parent)


class IdPrimaryKeyRelatedField(PrimaryKeyRelatedField):
    """

kai101

How to Install Wkhtmltopdf 12.4 with patched Qt?

• Fixed in 0.12.5 tested on ubuntu 18.04.
• wkhtmltopdf/wkhtmltopdf#3001 (comment)

For earlier version whos suffering from versionlock syndrome. Please follow the instructions to rollback to older SSL interface. Do not alarm by the fallback ssl interface, they received security patches for vulnerability discovered.

Current version of apt-get wkhtmltopdf does not come with Qt patch. There are some issue going with both Qt patched and non-patched. Most common use case is compatible with the patched Qt.