Building Pyo for Python3.14 with pyenv
Alexandros Drymonitis
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
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
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.
To view this discussion visit https://groups.google.com/d/msgid/pyo-discuss/CAFKYMmyk2EjR%3D8t%3DQv%3DVVEoQgq7VEhvDsFwasa%3DVg2gGne%3DxsQ%40mail.gmail.com.
Aaron Krister Johnson
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.