Taking over Pyo

52 views
Skip to first unread message

Alexandros Drymonitis

unread,
May 11, 2026, 1:54:51 AMMay 11
to pyo-discuss
With this message I want to let everyone know that Aaron, Sean and I have decided to take over Pyo, as it is obviously abandonware and we think it's too good to just die.
Two weeks ago I sent a message here addressing Olivier, to see if he replies. He didn't, so a week later I sent the same message in Pyo's GitHub conversations page and again got no reply.

We have now forked Pyo and it lives here https://github.com/pyo-org/pyo. We have tested it with Python3.14 on Linux and it works fine, but we do need Windows testers. We don't have wheels in PyPI yet, so anyone willing to test it should compile from sources.

Olivier had switched compiling from using the setup.py script, to `python3 -m build`, but the script still works fine (on Linux, at least, after Aaron refirbished it). If you want to compile Pyo with double precission, all you need to do (after installing dependencies) is `python3 setup.py --use-double`.

We still haven't created a documentation page, so you'll have to refer to the old one for compiling, https://belangeo.github.io/pyo/compiling.html. In there, Olivier writes: "Here is how you can compile pyo from sources on Linux and MacOS (if you are interested in the adventure of compiling pyo from sources on Windows, you can take a look at my personal notes in windows-10-64bit-build-routine.txt).". This is the page he refers to, https://github.com/belangeo/pyo/blob/master/scripts/win/windows-10-64bit-build-routine.txt.

Keeping Pyo alive has now become a collective effort, so your contribution is important. Windows users, please give some time to Pyo and try to run the latest with Python3.14 so we can finalize things. I'll be watching this thread and the group here, in case people have questions (that I can hopefully answer).

I'll keep everyone posted about how this is going.

All the best,
Alexandros

Tiago Bortoletto Vaz

unread,
May 14, 2026, 9:05:40 AMMay 14
to pyo-d...@googlegroups.com
Hello Alexandros and all involved,

Thanks for keeping pyo alive!

I'd like to be added to pyo-org as well. FWIW I'm the pyo/cecila/soundgrain
maintainer in Debian (and derivatives) and also the one hosting RadioPyo.

From time to time I might forward bugs reported in the Debian BTS to upstream
and who knows, perform the PRs myself.

(also had a chance of having Olivier as a teacher and supervisor, lots of
fun back then :-)

Bests,

--
Tiago Bortoletto Vaz
https://tvaz.cc

On Sun, May 10, 2026 at 10:54:50PM -0700, Alexandros Drymonitis wrote:
> With this message I want to let everyone know that Aaron, Sean and I have
> decided to take over Pyo, as it is obviously abandonware and we think it's
> too good to just die.
> Two weeks ago I sent a message here addressing Olivier, to see if he
> replies. He didn't, so a week later I sent the same message in Pyo's GitHub
> conversations page and again got no reply.
>
> We have now forked Pyo and it lives here https://github.com/pyo-org/pyo. We
> have tested it with Python3.14 on Linux and it works fine, but we do need
> Windows testers. We don't have wheels in PyPI yet, so anyone willing to
> test it should compile from sources.
>
> Olivier had switched compiling from using the setup.py script, to `python3
> -m build`, but the script still works fine (on Linux, at least, after Aaron
> refirbished it). If you want to compile Pyo with double precission, all you
> need to do (after installing dependencies) is `python3 setup.py
> --use-double`.
>
> We still haven't created a documentation page, so you'll have to refer to
> the old one for compiling, https://belangeo.github.io/pyo/compiling.html.
> In there, Olivier writes: "Here is how you can compile pyo from sources on
> Linux and MacOS (if you are interested in the adventure of compiling pyo
> from sources on Windows, you can take a look at my personal notes in
> windows-10-64bit-build-routine.txt
> <https://github.com/belangeo/pyo/blob/master/scripts/win/windows-10-64bit-build-routine.txt>
> ).". This is the page he refers
> to, https://github.com/belangeo/pyo/blob/master/scripts/win/windows-10-64bit-build-routine.txt.
>
> Keeping Pyo alive has now become a collective effort, so your contribution
> is important. Windows users, please give some time to Pyo and try to run
> the latest with Python3.14 so we can finalize things. I'll be watching this
> thread and the group here, in case people have questions (that I can
> hopefully answer).
>
> I'll keep everyone posted about how this is going.
>
> All the best,
> Alexandros
>
> --
> You received this message because you are subscribed to the Google Groups "pyo-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pyo-discuss...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/6f0a9e9f-ed64-4e3c-97bd-05a1c5f3d221n%40googlegroups.com.

Alexandros Drymonitis

unread,
May 14, 2026, 12:03:46 PMMay 14
to pyo-d...@googlegroups.com
Hi Tiago,

It's nice to see the team growing! I just sent you an invitation.

Cheers

Alexandros Drymonitis

unread,
May 15, 2026, 3:30:48 AMMay 15
to pyo-discuss
The core team of the new Pyo repository in the pyo-org GitHub organization now consists of five members, including Olivier! I think we're at a very good state where we can finalize Pyo-1.0.7 as stable, but we still need Windows testers. This message is addressing Windows users who want to help in keeping Pyo alive. We need at least one person to build Pyo-1.0.6 (the current source in https://github.com/pyo-org/pyo) for Windows so we can publish 1.0.7 in PyPI.

Of course, more people that want to become members of the development team are welcome. Just message me and I'll add you.

barmin

unread,
May 16, 2026, 3:30:06 AMMay 16
to pyo-d...@googlegroups.com
Hi everybody,

So happy to see that pyo is getting into motion again! Thanks to Alexandros, Sean and Aaron for the initiative, Tiago for joining in and of course Olivier for all the great work until now!

I'm not sure how much time I'll be able to give to this project, but I'm also interested in joining the team. My github username is amiguet,

Looking forward to see how things evolve from there!

Cheers,

Matthieu

Le 15.05.26 à 09:30, Alexandros Drymonitis a écrit :
> --
> You received this message because you are subscribed to the Google Groups "pyo-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pyo-discuss...@googlegroups.com <mailto:pyo-discuss...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/9b3b25b9-4a5a-46f8-abce-2bec80381ad5n%40googlegroups.com <https://groups.google.com/d/msgid/pyo-discuss/9b3b25b9-4a5a-46f8-abce-2bec80381ad5n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Olivier Bélanger

unread,
May 18, 2026, 1:11:50 PMMay 18
to pyo-d...@googlegroups.com
Hello,

I have a request for the pyo-org members... Can we delete the repo and re-fork it, but from belangeo/pyo? I have cleanup issues and pull requests in my repo, and it's just too painful on github to get pyo-org re-synced without belangeo/pyo being the fork parent! I suspect this will happen from time-to-time in the future, so I think now is a good time to make the change. I already have all the new changes merged in belangeo/pyo.

Cheers,

Olivier


To unsubscribe from this group and stop receiving emails from it, send an email to pyo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/38447538-b64f-4e5b-ab7e-8cac325d8231%40bluewin.ch.

Alexandros Drymonitis

unread,
May 18, 2026, 1:18:19 PMMay 18
to pyo-d...@googlegroups.com

Hi Olivier,

Please give me some time to update all the embedded stuff. What's left is the Bela, which I have managed to install Pyo but I have to confirm the steps needed for this. I'll do this tomorrow (maybe it will take a couple of days). I'll also upload tonight all the other stuff (I just updated the Pd stuff (I sent you a message in my pull request which you just closed) and I'll update OF and Juce), and from my side everything will be ready. You can then copy the embedded folder in your repo and we can delete and re-fork. What do you think?

Cheers,
Alexandros

Alexandros Drymonitis

unread,
May 18, 2026, 1:34:56 PMMay 18
to pyo-d...@googlegroups.com

I have now updated all embedded files but the Bela stuff. Pd, OF and Juce are all up-to-date with the projects that I managed to make work. As I wrote in my previous message, give me a couple of days and I'll get the Bela stuff updated too.

Olivier Bélanger

unread,
May 18, 2026, 1:46:13 PMMay 18
to pyo-d...@googlegroups.com
Hi Alex, no problem, I will keep my repo in sync, and when all pending work is merged, we re-fork!

Olivier

Aaron Krister Johnson

unread,
May 19, 2026, 4:49:38 PMMay 19
to pyo-d...@googlegroups.com
I'd like not to lose all the work I did on some of the install helper scripts. As long as the delete isn't destructive...what's the goal of the delete? Can't we work around the conflicts without nuking existing code?



Olivier Bélanger

unread,
May 19, 2026, 5:06:12 PMMay 19
to pyo-d...@googlegroups.com
Hi Aaron,

Nothing will be lost, I already cherry-picked your change in the pyo repo.

cherry-picks.png

It will just be way easier for me to re-sync the fork if it comes from belangeo/pyo, I already have a couple of pull requests merged that should also be in the pyo-org repo.

Olivier
 

Alexandros Drymonitis

unread,
May 20, 2026, 7:31:39 AMMay 20
to pyo-d...@googlegroups.com

Hi Olivier,

The Bela still gives me a hard time, but in the Pyo repository, all that is mentioned is the link to the Pyo-Bela repository. So, I think we can go on with the removal of the pyo-org repo and the re-import of your repository. Please make sure all the embedded stuff are the same between the two repos before giving the green light to delete pyo-org/pyo.

Cheers,
Alexandros

Olivier Bélanger

unread,
May 20, 2026, 6:34:49 PMMay 20
to pyo-d...@googlegroups.com
Hi Alexandros,

Every change has been pulled in my repo, we're good to delete and re-fork the repo!

Cheers,

Olivier


Alexandros Drymonitis

unread,
May 21, 2026, 1:41:21 AMMay 21
to pyo-d...@googlegroups.com

I have deleted the pyo-org repository but for some reason I can't import your repository. I keep getting an older version with the last update five years ago. The URL should be this https://github.com/belangeo/pyo right? Olivier, or someone else, can you give it a try and import your current master?

Alexandros Drymonitis

unread,
May 21, 2026, 2:05:11 AMMay 21
to pyo-d...@googlegroups.com

Nevermind, instead of importing it, I just forked it and it worked. We now have Olivier's latest repository in github.com/pyo-org/pyo.

Aaron Krister Johnson

unread,
May 22, 2026, 5:13:17 PMMay 22
to pyo-d...@googlegroups.com

Alexandros Drymonitis

unread,
May 23, 2026, 10:17:02 AMMay 23
to pyo-discuss
Olivier, I finally managed to get the Bela working and configured the correct steps. My repository (which is a fork of yours) is now up-to-date. Do you want to update yours so I can fork that for pyo-org, or you don't mind and I can just fork mine?
This wraps up the embedded section of Pyo. What's left is to test it on Windows. Next week I'll give it a try on a virtual machine and see how it goes.

Olivier Bélanger

unread,
May 23, 2026, 12:30:32 PMMay 23
to pyo-d...@googlegroups.com
Hi Alexandros, I think you can go with your repo, the time I can give to pyo, I’ll concentrate on the main lib! BTW, thank you for all the work you’ve put to make these side projects alive again, that opens a lot of opportunities! Maybe I will update my pyo-plugin for Wwise some day!

Cheers,

Olivier 

p.s...@outlook.com

unread,
May 27, 2026, 8:58:34 AM (11 days ago) May 27
to pyo-discuss
Just writing a quick message to thank everyone for coming together to move Pyo forward! This is really important software for some of us and I'm happy to see the community rallying around it. I've been enjoying getting a flurry of emails from this forum again.

I learned Python to use Pyo so I'm not much help with the development.

Warmly,
Paul
Reply all
Reply to author
Forward
0 new messages