Најди сличен содржај

Изворен канал @pythonotes · Post #418 · 9 мар.

Оператор pipe позволяет писать более компактный код, реализуя логику объединения данных (Union). Важно помнить, что его поведение зависит от контекста. Побитовые операции (логическое OR) result = 5 | 3 # 5 (0101) | 3 (0011) = 7 (0111) Самое главное - не путать с оператором or, это другое! Объединение множеств set_a = {1, 2, 3} set_b = {3, 4, 5} set_c = set_a | set_b # {1, 2, 3, 4, 5} set_c |= {5, 6} # {1, 2, 3, 4, 5, 6} Слияние словарей dict_1 = {"a": 1, "b": 2} dict_2 = {"b": 3, "c": 4} merged = dict_1 | dict_2 # {'a': 1, 'b': 3, 'c': 4} merged |= {"d": 5} # {'a': 1, 'b': 3, 'c': 4, 'd': 5} Аннотации типов, заменяет Union def process_data(value: int | str) -> None: print(value) Допустимо использовать в isinstance или issubclass isinstance(3, int | float) # True Паттерн-матчинг status_code = 404 match status_code: case 200 | 201 | 204: print("OK") case 400 | 404 | 500: print("ERROR") Для использования в своих классах требуется переопределить метод __or__ Так же нашел библиотеку pipe которая добавляет еще много возможностей. Рекомендую ознакомиться ;) #basic

Hashtags

#basic

Резултати

Пронајдени 3 слични објави

Пребарај: #jinja

当前筛选 #jinja清除筛选

djangoproject

@djangoproject · Post #562 · 27.01.2018 г., 07:22

Најди слично Погледај

https://medium.com/@Pinterest_Engineering/how-we-switched-our-template-rendering-engine-to-react-a799a3d540b0 How we switched our template rendering engine to #React In 2015, we made the decision to migrate our legacy web experience to React to keep up with our fast growth and perform better with increased developer velocity. When we began this project, Pinterest.com was humming along on the existing architecture for some time. On the server, #Django, a Python web application framework, served our web requests and #Jinja was rendering our #templates. The server response to the browser included all the markup, assets and data the browser needed to fetch our JavaScript, images and CSS, and initialize our client-side application. Nunjucks, a JavaScript template rendering engine that uses the same template syntax as Jinja, did all subsequent template renders on the client side.

Hashtags

#react #django #jinja #templates

djangoproject

@djangoproject · Post #362 · 03.07.2017 г., 19:33

Најди слично Погледај

https://stackoverflow.com/questions/30288351/how-to-setup-django-1-8-to-use-jinja2 The #Jinja template folder for app dirs defaults to #jinja2 not the standard templates folder. So try the following directory structure and #Django will locate your Jinja #templates: mysite mysite myapp jinja2 myapp index.html manage.py And instead of: return render(request, 'myapp/index.html') you should write: return render(request, 'index.html')

Hashtags

#jinja #jinja2 #django #templates

GitHub Trends

@githubtrending · Post #15412 · 14.01.2026 г., 16:30

Најди слично Погледај

#jinja#ansible#ansible_collection#collection#devsec#hacktoberfest#hardening#linux#mysql_hardening#nginx#nginx_hardening#os_hardening#playbook#protection#role#ssh_hardening#sysctl devsec.hardening is an Ansible collection that battle-tests security hardening for Linux (CentOS, AlmaLinux, Rocky, Debian, Ubuntu, etc.), MySQL, Nginx, and SSH, matching DevSec Inspec baselines. Install via `ansible-galaxy collection install devsec.hardening` and apply roles like os_hardening easily. It saves you time by automating secure configs across servers, cuts manual work, boosts compliance, and shrinks attack surfaces for safer systems. https://github.com/dev-sec/ansible-collection-hardening

Hashtags

#jinja #ansible #ansible_collection #collection #devsec #hacktoberfest #hardening #linux #mysql_hardening #nginx #nginx_hardening #os_hardening #playbook #protection #role #ssh_hardening #sysctl