Building Pyo for Python3.14 with pyenv

53 views
Skip to first unread message

Alexandros Drymonitis

unread,
Feb 16, 2026, 10:15:18 AMFeb 16
to pyo-d...@googlegroups.com
Hi all,

Since Aaron forked Pyo and got started on it, I tried to compile Pyo for
Python3.14 on my Debian 13 system (perhaps I'm impatient? sorry,
couldn't help it). I installed pyenv and installed python3.14.0a6 with
it (the available 3.14 versions from pyenv were 3.14.0a6, 3.14.0a6t,
3.14-dev and 3.14t-dev). I then `git clone`d Aaron's fork and followed
the instructions here to build
(https://belangeo.github.io/pyo/compiling.html). After the process
finished, it printed this:

```
Successfully built pyo-1.0.6.tar.gz and
pyo-1.0.6-cp314-cp314-linux_x86_64.whl
```

which placed these two files in pyo/dist. I did omit the last stage
though, which is `python3 -m pip install
dist/pyo-1.0.6-cp314-cp314-linux_x86_64.whl`, so it didn't work. When
running `pyenv exec python3` I did get python3.14.0a6 running (outside
Pyo's directory, because that does not allow import Pyo in a Python
session) and could do `from pyo import *` without getting an error, but
I couldn't even create a Server object.

I then tried the setup.py script, even though Olivier mentions here
(https://github.com/belangeo/pyo/discussions/293#discussioncomment-12426918)
that it shouldn't be used anymore, and it worked. I launched Python3.14
and imported Pyo and then created a Server and a Sine object and I got
sound! I then realized I missed the last part with the new build system,
and did `pyenv exec python3 -m pip install --force-reinstall
dist/pyo-1.0.6-cp314-cp314-linux_x86_64.whl` and it uninstalled and
reinstalled pyo-1.0.6 and again it worked.

I couldn't get wxPython to work yet, but I'm looking into this.

The good news is that Pyo runs fine with Python3.14 on Linux!

Aaron Krister Johnson

unread,
Feb 18, 2026, 6:35:30 PMFeb 18
to pyo-d...@googlegroups.com
Wanted to verify I got pyo compiled and built fine on Linux (Void Linux) using the latest system `python-3.14.2`, and using the scripts I have on my fork (https://github.com/akjmicro/pyo)

You should be able to, on Mac or Linux, separately download https://github.com/akjmicro/pyo/blob/master/scripts/get-pyo.sh

Run that, and in the directory you run it, it should clone the `pyo` sources, cd into them, and build. It _should_ automatically detect the python environment you're running at the time.

If you run into any issues or lack clarity, ping me here.

But at this point, I consider `pyo`'s being up-to-date a non-issue.



--
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/09b9001e-7d67-487e-927c-26111c1e0e0a%40gmail.com.

Alexandros Drymonitis

unread,
Feb 19, 2026, 2:54:11 AMFeb 19
to pyo-d...@googlegroups.com

This is good! What do you think should be the next steps? As I've already written, I want to include some pull requests on embedding Pyo in Pd and OF, but I'll need a few days to get them finished. Other than that, should we get a 1.0.7 stable version out?

I want to again share my concerns about the repository we're using. Aaron and I have discussed the open-source advantage where anyone can fork a project and work on it on their own, but if we want this software to become more stable, then a repository from a shared profile would be preferred, at least this is how I see it. The bus factor is one of the reasons I'm concerned about this. If there is a shared profile where all people that engage in developing Pyo can have access, if one of them leaves the project, we won't have to start over with a new fork and a new URL where people can download the latest and greatest version.

Aaron Krister Johnson

unread,
Feb 19, 2026, 1:40:11 PMFeb 19
to pyo-d...@googlegroups.com
Let's try to get Olivier to pull my changes into master...? It may take a while.

I will let someone else handle release packaging, at the moment, I don't want to maintain pip releases for different platforms, etc....I'm satisfied being a tester who knows I can build this thing on various platforms. :D

To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/2fc153aa-a051-459f-8135-e8f93c094639%40gmail.com.

Alexandros Drymonitis

unread,
Mar 18, 2026, 3:41:20 PMMar 18
to pyo-discuss
Hi Aaron and whoever else might be following this discussion.
It's now a month since your last reply in this thread, and a year since Olivier appeared answering to any of Pyo's communication channels. Should we consider Pyo abandonware?
I have managed to run all the embedded projects of Pyo with Pyo-1.0.6 and Python 3.13 (except from the Bela whose latest image has Python3.11). These are Pure Data, openFrameworks, JUCE (an audio plugin) and the Bela. I need to finalize some things in the Bela process and a coupld of additions in the openFrameworks example and this section will be ready. I'll then make a pull request to your fork and I really think we should consider publishing.

What are your thoughts on this?

Sean Wayland

unread,
Mar 18, 2026, 7:51:54 PMMar 18
to pyo-d...@googlegroups.com

Hey everyone,

Just a thought on how we could move forward here.

Why not create a new public GitHub repo and push the existing history as-is? Then we can set up a few admins who have permission to merge PRs, and lock down the main branch so merges only happen through them.

With that setup, anyone can fork the repo and open a PR, but we still keep control over what gets merged. The nice part is having multiple admins—so if someone disappears or is unavailable, things don’t get blocked. We could also ask Olivier to be one of the admins.

I’d suggest keeping the LGPL-3 license as it is.

Also, are you planning to set up a build/test pipeline using GitHub Actions and cibuildwheel? It would be great if it could also handle publishing to PyPI automatically.

Curious what everyone thinks.

Best,
Sean




To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/8df7cf6b-39f9-42f8-8f89-8a99f951d5f1n%40googlegroups.com.


--


http://seanwayland.com

https://github.com/seanwayland



Sean Wayland           

US cell phone: +1 (347)5231455


Message has been deleted

Alexandros Drymonitis

unread,
Mar 19, 2026, 2:59:59 AMMar 19
to pyo-d...@googlegroups.com
On 3/19/26 01:51, Sean Wayland wrote:
>
> Hey everyone,
>
> Just a thought on how we could move forward here.
>
> Why not create a new public GitHub repo and push the existing history
> as-is? Then we can set up a few admins who have permission to merge
> PRs, and lock down the main branch so merges only happen through them.
>
> With that setup, anyone can fork the repo and open a PR, but we still
> keep control over what gets merged. The nice part is having multiple
> admins—so if someone disappears or is unavailable, things don’t get
> blocked. We could also ask Olivier to be one of the admins.
>
I agree with you. I also think it's not elegant if Pyo is in the
repositories of one of the admins. It looks better if it's
github.com/pyo/pyo.
I definitely agree that we could ask Olivier to be part of this (and I
wish he is), but I'm not very optimistic about it since he hasn't shown
any signs of existence for a year now.

> I’d suggest keeping the LGPL-3 license as it is.
>
I agree.
>
> Also, are you planning to set up a build/test pipeline using GitHub
> Actions and cibuildwheel? It would be great if it could also handle
> publishing to PyPI automatically.
>
I know very little about GitHub actions, someone else might know more
and how to set it up. Also, I've never published anything to PyPI
either, so whoever is more knowledgeable could help with this too.

Darren Sholes

unread,
Mar 19, 2026, 12:01:16 PMMar 19
to pyo-discuss
Hi all,

Been passively monitoring this discussion. I don't really have capacity at the moment to admin this, but one thing I've done in the past for a different shared project that was helpful was to start a Github Organization. It makes it feel more like the project doesn't "belong" to one person and makes managing admins easy. Then fork `pyo` and have the organization be the "owner".

RE Github Actions, for public repos, I believe the runners are free and unlimited (no quotas). Olivier has an existing workflow for the linux wheels here, so you can use that as a starting point.  They're essentially just YAML files that describe a process for running a set of commands in order.

Olivier opened up the "Discussions" feature on the existing repo, so if you do plan to create an Org and fork, you should probably announce it on the Discussions as well, so people who aren't part of this Google Group are aware.

Best,
Darren

Aaron Krister Johnson

unread,
Mar 19, 2026, 2:51:30 PMMar 19
to pyo-d...@googlegroups.com
+1 on this idea.

My fork (under my github link below) can be used as the starting point of the codebase, since I've done significant work adding niceties to the build-script process.

--
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/e46cdd32-d369-4c06-acfa-0ab239cb5d5cn%40googlegroups.com.

Alexandros Drymonitis

unread,
Mar 19, 2026, 3:48:57 PMMar 19
to pyo-d...@googlegroups.com

I just tried to create an organization, but the name "pyo" is taken (I guess, it's Olivier's repository). How should we name it? Ideas?

Darren Sholes

unread,
Mar 19, 2026, 3:58:58 PMMar 19
to pyo-d...@googlegroups.com
pyo-org?

You received this message because you are subscribed to a topic in the Google Groups "pyo-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pyo-discuss/LtAkRgyYnYc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pyo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/da293807-406d-47f5-b095-c80449defae7%40gmail.com.

Aaron Krister Johnson

unread,
Mar 19, 2026, 4:32:35 PMMar 19
to pyo-d...@googlegroups.com
that works for me
To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/CAG0P6Mxo8aJ5%2BNgh1X3j7LuqnzSVHxa9TpS_5OiXzvx%3DYEQJJg%40mail.gmail.com.

Alexandros Drymonitis

unread,
Mar 24, 2026, 4:55:16 AMMar 24
to pyo-d...@googlegroups.com

I just created a pyo-org organization on github and imported Aaron's fork of pyo. I already added Aaron to the organization. Who else wants to be involved in this? Let me know and I'll add you as well.

Since we have verified that Pyo runs on Python3.14, and I have completed (nearly) the embedded part, I think it's a good time to wrap things up and announce a release. What do you think?

Alexandros Drymonitis

unread,
Mar 24, 2026, 5:44:57 AMMar 24
to pyo-d...@googlegroups.com

It's funny that I imported Aaron's fork, but the repository that was created was Olivier's. I have no idea why this happened, so if anyone can help with that, I would appreciate it.

Aaron Krister Johnson

unread,
Mar 24, 2026, 10:07:20 AMMar 24
to pyo-d...@googlegroups.com
The earliest I can help with this is Friday. I'm working and friends are in town off-hours. Thanks for taking the initial steps, though, Alexandros.

To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/0e6ef2e9-d5cb-4563-9c21-7c8116792171%40gmail.com.

Alexandros Drymonitis

unread,
Mar 29, 2026, 11:23:06 AM (9 days ago) Mar 29
to pyo-d...@googlegroups.com

I have successfully forked your fork, Aaron. I have also finalized the openFrameworks example and in the next few days I will finalize the Bela integration of Pyo. Then I'll be done with what I needed to do.

Anyone else thinks there's more left to do?

Anyone else wants to join this github organization?

Sean Wayland

unread,
Mar 29, 2026, 1:02:03 PM (9 days ago) Mar 29
to pyo-d...@googlegroups.com
i would like to join thanks 

To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/e5f61f0d-49f9-4a36-b0ae-e8aadad7543f%40gmail.com.
Reply all
Reply to author
Forward
0 new messages