This article starts a new series of blog posts about “bug hunts”. In these articles, I will go through a recent bug in Brian (or one of its dependencies) and describe all the steps I used to find the source of the bug and how I fixed it. I will try to not only focus on the Brian-side of things, but also show some general tools like git bisect or “monkey patching” that can be helpful to find the source of these nasty critters (no actual bugs were harmed during the making of this blog post).

Let’s start! Today’s bug will be about equations, and more specifically about their LaTeX representation. As most of you probably know, Brian can represent equations, quantities, etc. in LaTeX. This representation can then either be included in a LaTeX document or directly rendered for example as the output in jupyter notebooks.

Read more…

Marcel Stimberg will talk about Brian’s development process in a live developer session on Thursday, Feb 11 2021, 17:00 UTC (check local time). For more information and the link to the Zoom session see the announcement.

Read more…

In these very particular times, we are nevertheless happy to announce a new release, Brian 2.4. This release fixes a large number of bugs and includes a number of small improvements. As announced with the previous release, Brian 2.4 is the first release that no longer supports Python 2. For a full list of changes, see the release notes. We recommend all users of Brian 2 to update.

Read more…

Happy New Year to all Brian users 🎉! We are happy to announce a new release, Brian 2.3. This release fixes a number of bugs and introduces some new features. It also paves the way for the transition from Python 2 to Python 3 – given that Python 2 is now no longer officially supported, Brian 2.3 will be the last release to support Python 2. For a full list of changes, see the release notes. We recommend all users of Brian 2 to update.

Read more…