<?xml version="1.0" encoding="utf-8" standalone="no"?><rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" version="2.0"><channel><title>Alexey Evseev</title><description></description><managingEditor>noemail@noemail.org (Alexey Evseev)</managingEditor><pubDate>Mon, 2 Sep 2024 07:55:35 GMT</pubDate><generator>Jekyll https://jekyllrb.com/</generator><link>https://st4lk.github.io/en/</link><language>en-us</language><item><title>SQLALchemy vs Django ORM</title><link>https://st4lk.github.io/en/blog/2023/12/09/sqlalchemy-vs-django-orm/</link><category>python</category><category>sqlalchemy</category><category>orm</category><category>django</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Sat, 9 Dec 2023 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2023/12/09/sqlalchemy-vs-django-orm</guid><description>If you are working with Django ORM most of the time and then switching to SQLAlchemy - you may face some unexpected behavior. In this post I’ll try to describe the most important differences from my point of view. All examples for SQLAlchemy will be shown in async code, in context of PostgreSQL. Django version - 4.2, SQLAlchemy version - 2.0. The full examples can be found here https://github.com/st4lk/sqlalchemy-vs-django-orm, in the article the code will be cutted to be short.</description><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://st4lk.github.io/en/assets/images/posts/2023-12-09-sqlalchemy-vs-django-orm/sqla_vs_django_upd.png"/><media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://st4lk.github.io/en/assets/images/posts/2023-12-09-sqlalchemy-vs-django-orm/sqla_vs_django_upd.png"/></item><item><title>Sublime Text and Language Server Protocol</title><link>https://st4lk.github.io/en/blog/2019/02/19/sublime-text-and-language-server-protocol-lsp/</link><category>python</category><category>sublime</category><category>lsp</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Tue, 19 Feb 2019 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2019/02/19/sublime-text-and-language-server-protocol-lsp</guid><description>Language Server Protocol (LSP) LSP - protocol for interactions between IDE and language server. The latter provides such means like autocompletion, goto implementation and etc. When IDE needs to show autocomplete choices on, for example, python language - it sends a request to the special server. And it responds with the necessary data. The cool part here is that it is an initiative of a big company - Microsoft.</description><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://i.ibb.co/4K4zp06/sublime-256-lsp-light.png"/><media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://i.ibb.co/4K4zp06/sublime-256-lsp-light.png"/></item><item><title>Trap in counting related objects in Django</title><link>https://st4lk.github.io/en/blog/2017/01/14/count-filtered-related-objects-django/</link><category>database</category><category>django</category><category>sql</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Sat, 14 Jan 2017 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2017/01/14/count-filtered-related-objects-django</guid><description>Task: for every object count number of related objects satisfying some conditions.</description></item><item><title>Django: signal or model method?</title><link>https://st4lk.github.io/en/blog/2016/08/01/django-signal-or-model-method/</link><category>django</category><category>signal</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Mon, 1 Aug 2016 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2016/08/01/django-signal-or-model-method</guid><description>When I needed to implement some functionality on model saving, I always asked a question to myself - where to place it. In signal or in model method save()? Let’s see, what and when is more applicable.</description></item><item><title>Trying JSON in Django and PostgreSQL (and compare with MongoDB)</title><link>https://st4lk.github.io/en/blog/2015/09/30/trying-json-combo-django-and-postgresql/</link><category>database</category><category>django</category><category>mongodb</category><category>postgresql</category><category>sql</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Wed, 30 Sep 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/09/30/trying-json-combo-django-and-postgresql</guid><description>New JSONField will be added in Django 1.9, it can be used with PostgreSQL &amp;gt;= 9.4. Let’s try to work with it and find out, in what situations it can be useful.</description></item><item><title>OAuth and django rest framework</title><link>https://st4lk.github.io/en/blog/2015/07/18/oauth-and-django-rest-framework/</link><category>api</category><category>django</category><category>oauth</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Sat, 18 Jul 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/07/18/oauth-and-django-rest-framework</guid><description>Star This is a well known topic, but i can’t find the existing solution that will fully satisfy me. So i write it by myself :). Assume we have a “single page” web site, that is talking with backend via REST API. Client side can be written with ember, angularjs or some like this. Backend - django rest framework (DRF). We’ve got a task - add social login (OAuth protocol).</description></item><item><title>Tornado and pgettext</title><link>https://st4lk.github.io/en/blog/2015/06/05/tornado-and-pgettext/</link><category>i18n</category><category>tornado</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Fri, 5 Jun 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/06/05/tornado-and-pgettext</guid><description>Recently (26.05.2015) new tornado 4.2 was released. It contains different updates, the most valuable i suppose are modules tornado.locks and tornado.queues. They migrated from package Toro, look detailed explanation in Jesse Jiryu Davis post. Here i want to tell about another helpful function, that was added with my help - pgettext.</description></item><item><title>OAuth step by step</title><link>https://st4lk.github.io/en/blog/2015/05/16/oauth-step-step/</link><category>api</category><category>oauth</category><category>security</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Sat, 16 May 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/05/16/oauth-step-step</guid><description>Gist OAuth protocol has two versions: 1.0 and 2.0. Most of services today use version 2.0, i suppose because it is easier to implement. Also, 2.0 can be realized in standalone applications (those, that don’t have a server). To understand the protocols very useful to have a look at their realisation. Here i’ll show several scripts that talk to OAuth providers of different versions. Scripts will implement client application functionality. Only standard python libraries are used. This help to overview the OAuth protocol - everything is on single screen and familiar. Of course, for production application we must use third party oauth libs, they handle many special cases and so on. Purpose of these scripts is just understanding of the protocol and nothing else. It is often hard to keep the protocol flow in production-ready library, because it is splitted in many modules, some other packages are used. And the full vision is slipping out of sight.</description></item><item><title>Python tips &amp;amp; tricks</title><link>https://st4lk.github.io/en/blog/2015/04/30/base-python-tips-tricks/</link><category>python</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Thu, 30 Apr 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/04/30/base-python-tips-tricks</guid><description>Recently i’ve read the book Learning Python, 5th Edition by Mark Lutz. Here is a list of most interesting insights for me.</description></item><item><title>Listen wifi with wireshark</title><link>https://st4lk.github.io/en/blog/2015/04/17/listen-wifi-with-wireshark/</link><category>fun</category><category>security</category><author>noemail@noemail.org (Alexey Evseev)</author><pubDate>Fri, 17 Apr 2015 18:19:43 GMT</pubDate><guid isPermaLink="false">https://st4lk.github.io/en/blog/2015/04/17/listen-wifi-with-wireshark</guid><description>I always knew, that it is possible to catch wifi network packets. But haven’t done it in practise (i was analysing network packets, but not in HTTP protocol). So i decided to do it, as this is interesting and useful. Such experience help to understand TCP-IP and HTTP protocols and also to pay more attention for web security.</description></item></channel></rss>