Writing is a kind of code
CourtBouillon conceives high-quality apps and tools to help you give life to elegant documents, wonderful images, lovely texts, and more.
In about a year, we’ve got an increasing number of pull requests and security reports. A lot of contributions, that’s good news! Well… No. They look like contributions, but they’re not. They’re a new kind of poison that kills free software projects all around the world.
That’s a recurring question on our bug trackers: why don’t you add type annotations to your Python projects? That’s a good question, and it needs an article to really explain why.
Ruff is a code formatter and linter for Python. It’s so fast and so powerful that it has already replaced Black, isort or Flake8 in many open source Python projects. And that’s just the start: Ruff’s creator has raised 4 million dollars and now wants to "fix" the Python ecosystem once and for all.
Do you read this post on Google Chrome? Probably, as almost everybody does, but… Do you read it on your good old personal computer, in the bathroom on your smartphone, in your bed on your game console? Or maybe you’re listening to the article thanks to a voice synthesis? Chrome is everywhere, but the diversity of its uses may actually save web diversity.
Do you read this post on Google Chrome? Statistically, it’s highly probable. And if you’re on another browser, don’t worry, you won’t have the choice for long…
OK, the title is a bit dramatic, but we have to face it: the situation is serious in the small world of web browsers. Little by little, users lose what should be theirs. And if you’re reading this, it means that you’re one of the users.
Here we are. We untied knots, dug down to the roots, dissected formats, scattered files, opened a toolbox and defined needs. Maybe we can now think about making a package!
Python packaging can sometimes be a nightmare. It’s all the more hellish because when we talk about package creation and installation, we should first start to define precisely what we mean.
Python packaging can sometimes be a nightmare. To create, share and install packages, there are a lot of tools, sometimes doing the same thing, but not the same way.
Python packaging can sometimes be a nightmare. To convince yourself about that, you just need a few minutes of drowning into the myriad of usable (and used!) files to build or install a packages.
Python packaging can sometimes be a nightmare. But, by the way, what is a package? Obviously, as nothing is simple, as nothing will be spared, the non-answer to this question is: it depends…
Python packaging can sometimes be a nightmare. Because of the stupidity of Python maintainers? What if it was more complicated?
Python packaging can sometimes be a nightmare. You don’t know what we’re talking about? Let’s present you a couple of things and we’ll talk again after that…