Python Company’s Post

Lookie here! Our Python DAW-Project repo just hit 41 stars and 3 forks. Great to see people finding it useful. DAWProject is an open XML-based format for exchanging full session data between DAWs, so producers and engineers can move projects without losing important information. The original repo from Bitwig was written in Java. At RoEx we work mainly in Python and C++, so we converted the core classes to Python. Big thanks to Bitwig for creating the spec. We love the idea of DAWProject and want to see it in every DAW. The more people building on it, the better, so we've made our Python version public. Fork it, extend it, turn it into a pip package, whatever you like. https://lnkd.in/e_6p_3in

How to Create a Simple HTTP Server in Python Creating a quick and simple (non-production) static file server is quite simple in Python. This article gives the details and a few examples for the Python beginner. #python #pythonhowtos #pythonhttpserver #httpserver #programming https://lnkd.in/eqMCBV72

A new post on how to extend Nighthawk with Python Modules, including new scripts for the TrustedSec SA, Remote and Injection BOF repos......Extending Nighthawk with Python Modules - https://lnkd.in/eXHcYf9h

This article by Bala Priya C explains how the builder pattern can simplify the process of creating complex objects in Python. I found it interesting that the pattern alleviates issues like overly complicated constructors and optional arguments that many developers face. It’s a great reminder of how design patterns can enhance code readability and maintainability. Have you used the builder pattern in your projects? What was your experience like?

🐍📰 A First Look at PyScript: Python in the Web Browser In this tutorial, you'll learn about PyScript, a new framework that allows for running Python in the web browser with few or no code modifications and excellent performance. #python

I've been programming in Python for 16 years (it was the first programming language I learned) and I have suffered through the travails of the Python 2 → 3 shift, the deluge of type hints in Python 3.5, the debates over spaces vs tabs, the rise of automatic formatting & linting, and the rise and fall of numerous package managers. The biggest struggle for me in all of this has been packaging; the Python language was already well established before it released an official third-party software repository (PyPI was released in 2003) and it failed to build a comprehensive and universal solution for packaging and distribution. I've built software using pip, pipenv, pdm, poetry, hatch, conda, and others, and they were all a constant pain in their own unique ways. Things are much easier now with the rise of the latest generation of package managers (pixi by prefix.dev and uv by Astral). I wanted to better understand how things got this way, so I decided to write a blog post (which meant I needed to start a blog): https://lnkd.in/gy85jmDq I plan to write a series of articles on modern software development practices in Python over the next few weeks, so stay tuned.

🚀 How to Write Clean & Understandable Python Code 🐍 Clean code is not just about making programs work — it’s about making them easy to read, easy to maintain, and easy to scale. In this post, I’ve highlighted: ✅ Meaningful variable & function names ✅ Following PEP 8 standards ✅ Writing modular and reusable functions ✅ Proper comments & doc strings ✅ Error handling best practices ✅ DRY principle (Don’t Repeat Yourself) ✅ A simple real-world Python example that ties everything together 💡 Why clean code matters? Because code is read more often than it is written — by teammates, reviewers, and even your future self. If you’re a beginner, this will help you build strong foundations. If you’re experienced, it’s a great reminder of best practices we should never skip. 👉 Swipe / view the image for a quick and clear guide. Let me know in the comments💬: What’s one clean-code habit you always follow in Python? 👇

I have just finished Packt's book: Asynchronous Programming in Python by Nicolas Bohorquez. It's very easy to follow, you can get through all of it during a weekend. It delves into how Python Global Interpreter Lock (GIL) works, the challenges it represents for async programming and how to work around it to improve your python application performance. Throughout the book you will see how to boost performance by making the execution of your Python code asynchronous using the traditional approach (asyncio), and Nicolás does a great job explaining asyncio limitations and what issues the Trio library solves. You will learn the following: * Profile your async Python code using py-spy, scalene and memray. * Unit-test your async python code with pytest-asyncio. * Debunk common myths about async performance improvements. * Boost your DJango, Flask and Quart app performance by making it async and using aiohttp for handling non-blocking requests. If you are a Python backend developer, I highly recommend you to read this book. Thanks Packt and Vinishka Kalra for sending me this book for review.

The latest release of the uv package manager for Python (https://lnkd.in/giiSEK3b) adds awareness of ROCm 7.1 to the --torch-backend flag. On ROCm platforms, packages with a dependency on torch can also automatically install the appropriate build of PyTorch using a command of the form: uv pip install [package with torch dependency] --torch-backend=auto Thanks to Charlie Marsh for implementing this so quickly after the PyTorch 2.10 release. I've posted about this before, but it's still magical to me.