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
This article offers key insights into the ISTQB certification and shares a proven preparation strategy to help candidates succeed.
In the previous article, we learned about test analysis for a product in general, and now we are ready to go further and look at test analysis for specific features.
One of our recent projects includes the functionality of an inline code editor. This code editor needed to be highly extensible and have custom features. To address this, we chose Codemirror v6 due to its peculiar architecture - it is highly customizable, and all the additional features are provided into codemirror engine as Extension objects.
This article is aimed for beginners, who are trying to choose between Ruby on Rails and Django. Let’s see which is fastest and why.
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.
Everybody knows about permalink, but it's usually used only in get_absolute_url. I prefer to use it for all related model urls.class Event(models.Model):# ...@models.permalinkdef edit_url(self):return ('event_edit', (self.pk, ))And then in template:<a href="{{ event.edit_url }}">Редактировать событие</a>