It appears that not everyone knows that in python you can create classes dynamically without metaclasses. I'll show an example of how to do it.
So we've learned how to use custom QuerySet to chain requests:
Article.objects.old().public()Now we need to make it work for related objects:
user.articles.old().public()
This is done using use_for_related_fields, but it needs a little trick. Thing is that in django related managers are initialized without arguments, and our QuerySetManager takes argument - queryset class.
objects = QuerySetManager(MyQuerySet)We have to update QuerySetManager in such a way, that will allow setting queryset as class field:
class QuerySetManager(models.Manager):
use_for_related_fields = True
queryset_class = QuerySet
def get_query_set(self):
return self.queryset_class(self.model, using=self._db)
def __getattr__(self, key):
return getattr(self.get_query_set(), key)In order to use this manager, we have to create a sublcass and set queryset_class:
class MyManager(QuerySetManager):
queryset_class = MyQuerySetIt's not fun to create such class every time. So we'll write a function that does it for us:
def queryset_manager(qs_class):
class Manager(QuerySetManager):
queryset_class = qs_class
return Manager()Now it's enough to write:
objects = queryset_manager(MyQuerySet)Subscribe for the news and updates
One of our ongoing projects, Neptyne, introduces an Excel-like grid written in React. We used a library to apply virtual scroll to it, but we stumbled upon a problem with fixed rows and columns inside the grid. Here I would like to describe this problem, how it occurs, and how we handled it.
Lead management is an important part of the marketing strategy of every company of any size. Besides automating various business processes, privately-held organizations should consider implementing an IT solution that would help them manage their leads. So, how should you make a web-based leads management system for a University in order to significantly increase sales?
In this article we will write a small library for pulling metadata and creating a preview for a site just like Slack does.
When we use css-sprites it's important to make browser cache them for longest period possible. On other hand, we need to refresh them when they are updated. This is especially visible when all icons are stored in single sprite. When it's outdated - entire site becomes ugly.
There was a task to submit form with ajax, with server side validation of course. Obvious solution is to do validation and return json with erros. I didn't like idea of writing separate view for validation and then inserting errors in form html on client side. Especially since I already had a generic template for django form with errors display. In this article I'll describe how I solved the task.
Usually users' profiles are stored in single model. When there are multiple user types, separation is made by some field like user_type.Situation is a little more complicated when different data is needed for each user type.In this article I'll describe how I solve this task.